Access Token
A digital credential used for authentication and authorization, issued by a server and carried by the client in subsequent requests to prove identity and permissions.
Timeline (last 90 days)
Claude bypassed the paywall by requesting an access token that the website automatically issued on its own, rather than cracking encryption; the vulnerability was lax parameter or permission validation logic.
For long-running AI tasks, synchronous refresh of access tokens on the critical path should be avoided.
The pattern of short tokens plus long refresh reduces token exposure risk while avoiding frequent user re-login.
An access token is usually a string with an expiration (such as a JWT); once leaked, an attacker can impersonate the identity within its validity period.
For AI applications, it is recommended to keep the access token lifetime short and use the refresh mechanism to maintain the session.
DPoP's protection of refresh tokens reduces the scope of impact after a token leak, but access tokens remain Bearer, and an access token leaked within its validity period can still be abused.
Google recently introduced a DPoP (Demonstrating Proof of Possession) binding mechanism for OAuth refresh tokens, binding refresh tokens to client keys while access tokens remain in Bearer form.
In OAuth 2.0, access tokens are used to call resource server APIs and typically have a lifetime of minutes to hours; refresh tokens are used to obtain new access tokens and can have a lifetime of days to months.
After an API key leaks, it must be manually revoked and recreated in the service provider's console; access tokens can be invalidated immediately via a revocation endpoint.
API keys are usually long-lived static strings used to identify the caller and for billing, and many service providers do not support fine-grained scopes, whereas access tokens often have expiration times, scopes, and revocability.
2 more timeline events
All Facts (12)
In traditional web applications, access tokens are typically set with short expiration periods (such as 15 minutes to 1 hour), combined with refresh tokens to achieve seamless renewal.
70%UnverifiedClaude bypassed the paywall by requesting an access token that the website automatically issued on its own, rather than cracking encryption; the vulnerability was lax parameter or permission validation logic.
50%UnverifiedFor long-running AI tasks, synchronous refresh of access tokens on the critical path should be avoided.
50%UnverifiedAn access token is usually a string with an expiration (such as a JWT); once leaked, an attacker can impersonate the identity within its validity period.
50%UnverifiedThe pattern of short tokens plus long refresh reduces token exposure risk while avoiding frequent user re-login.
50%UnverifiedFor AI applications, it is recommended to keep the access token lifetime short and use the refresh mechanism to maintain the session.
50%UnverifiedIn OAuth 2.0, access tokens are used to call resource server APIs and typically have a lifetime of minutes to hours; refresh tokens are used to obtain new access tokens and can have a lifetime of days to months.
50%UnverifiedGoogle recently introduced a DPoP (Demonstrating Proof of Possession) binding mechanism for OAuth refresh tokens, binding refresh tokens to client keys while access tokens remain in Bearer form.
50%UnverifiedDPoP's protection of refresh tokens reduces the scope of impact after a token leak, but access tokens remain Bearer, and an access token leaked within its validity period can still be abused.
50%UnverifiedAPI keys are usually long-lived static strings used to identify the caller and for billing, and many service providers do not support fine-grained scopes, whereas access tokens often have expiration times, scopes, and revocability.
50%UnverifiedAfter an API key leaks, it must be manually revoked and recreated in the service provider's console; access tokens can be invalidated immediately via a revocation endpoint.
50%UnverifiedThe white paper favors using access tokens for agents that are extremely narrow in scope, extremely short in validity, and bound to specific task contexts.
50%