Protocols
Saved & recent

Token revocation

Also called: OAuth token revocation, RFC 7009

Token revocation ends a token’s acceptance before its ordinary expiry. OAuth defines an endpoint where a client can ask the authorization server to invalidate a refresh or access token. Which related tokens also become invalid depends on the token type and server policy. Deleting a local copy alone does not revoke another copy.

For example, disconnecting a calendar integration can revoke its refresh token so it cannot obtain more access tokens. Already-issued access tokens require enforcement too. An API that only checks a JWT’s signature and expiry offline does not automatically learn about revocation; it needs an additional state-checking or notification mechanism, or must rely on expiry to bound continued acceptance.

Read first
OAuth 2.0
Related
Refresh token, Token introspection, JWT claims validation
Further reading
IETF RFC 7009 — OAuth 2.0 Token Revocation
revoke refresh token calendar integration authorization server future refreshes blocked existing access token resource API check fresh revocation state signature and expiry only rejects token may accept until expiry
Revoking R stops future refreshes. Whether related access token A is also revoked depends on policy. A fresh state check can enforce A’s revocation; signature and expiry checks alone do not learn about the later event.

View in the full Protocols collection