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
- Further reading
- IETF RFC 7009 — OAuth 2.0 Token Revocation