access token
A generated string that proves who you are to a service, used instead of a password and revocable on its own.
Anyone holding a token can act as you until it expires or is revoked.
In more detail
Services prefer tokens because they can be limited in scope (for example read-only) and in lifetime, and revoked without changing your password. Treat them exactly like passwords.
Examples
Flux bootstrap needs a GitHub token to push its manifests; give it the smallest useful scope.GitHub personal access tokens are used for pushing over HTTPS.A stolen cloud access token keeps working after the victim's password is reset, until its sessions are revoked.Related terms
- bearer token — A token that grants access to whoever presents it, sent as Authorization: Bearer <token>, without any further proof of identity.
- OAuth 2.0 — A framework for delegated authorization: a user lets an application call an API on their behalf without giving it their password.
- OAuth scope — A named permission a token carries, such as tasks:read or tasks:write, limiting what the token may be used for.
- audience — The recipient a token is meant for, named in its aud claim, such as one particular API.
- refresh token — A longer-lived credential a client uses to get a new short-lived access token without asking the user to log in again.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- flux bootstrap — The one-time Flux command that installs the Flux controllers on a cluster and commits their manifests to a Git repository so Flux then manages itself.
- GITHUB_TOKEN — A short-lived access token GitHub creates for each job so the workflow can call the GitHub API for its own repository.
- docker login — Signs the Docker CLI in to a registry so you can push, or pull private images.
- JSON Web Token — A compact signed token made of three base64url parts separated by dots: a header, a payload of claims and a signature.
- ID token — The signed token in OpenID Connect that tells a client who the user is and how they authenticated, meant for the client rather than for APIs.
- leaked secret — A password, token or key that has been exposed, for example by being committed to a repository, and must be treated as known to others.
- authentication — Establishing who a request represents, for example by checking a password, a session cookie or a signed token.
- key rotation — Replacing a password or key with a new one on a schedule or after a suspected leak, and re-encrypting what it protected.
Taught in
- Remote Servers And Trust — AI Engineering: LLM Apps, RAG & Agents
- Basic Auth, Tokens And Sessions — Modern API Architecture: REST, GraphQL & gRPC
- OAuth Two And OpenID Connect — Modern API Architecture: REST, GraphQL & gRPC
- Bootstrapping Flux on a Cluster — Continuous Integration & Continuous Delivery Pipelines
- Authenticate, Tag, Push And Pull From A Registry — Docker Architecture & Production Containers
- Authentication: JWTs and Claims — Modern .NET Core, C# & Enterprise Microservices
- Session Architecture: HTTP-Only Cookies vs Tokens — Production Full-Stack Engineering
- OAuth2 & OpenID Connect: Social Auth & PKCE Flows — Production Full-Stack Engineering
- JWT Verification: Asymmetric Keys & Refresh Rotation — Production Full-Stack Engineering
- Traffic Management: Sliding Window Rate Limiting — Production Full-Stack Engineering
- Conventional Commits — Advanced Git Internals & Distributed Workflows
- Ignoring Files, And The Tracked File Trap — Advanced Git Internals & Distributed Workflows
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- Bootstrap A Local Cluster And Check Your Context — Kubernetes: Production-Grade Container Orchestration
- Authentication, ServiceAccounts And Short Lived Tokens — Kubernetes: Production-Grade Container Orchestration
- kubeadm, High Availability And Cluster Lifecycle — Kubernetes: Production-Grade Container Orchestration
- Containment & Eradication: Host, Net & Identity — Security Operations & Threat Hunting (SOC)
- Why Secrets Leak — Application Security & Threat Modeling for Engineers
- The Environment Variable Trap — Application Security & Threat Modeling for Engineers
- Workload Identity — Application Security & Threat Modeling for Engineers
- Secret Scanning — Application Security & Threat Modeling for Engineers
References
- RFC 6749: The OAuth 2.0 Authorization Framework
- RFC 6750: OAuth 2.0 Bearer Token Usage
- GitHub Docs: Managing your personal access tokens
- Docker Hub: personal access tokens
- OWASP Secrets Management Cheat Sheet
- RFC 6749: OAuth 2.0 (access token)
- OWASP Session Management Cheat Sheet