Token introspection
Also called: OAuth token introspection, RFC 7662
Token introspection lets an authorized service ask an OAuth authorization server about a token’s current status and associated metadata. The response includes active and may include scope, audience and expiry. It can be used with different token formats; an opaque token is a common use case, not a requirement.
For example, a printing API submits a token to its trusted introspection endpoint and receives active: true with a read-only scope. That does not permit starting a print job: the API still checks the requested operation. Caching introspection results reduces traffic but can delay recognition of revocation, creating a deliberate freshness tradeoff.
- Read first
- OAuth 2.0
- Related
- OAuth 2.0, Token revocation, Bearer token
- Further reading
- IETF RFC 7662 — OAuth 2.0 Token Introspection