Token endpoint
RFC 6749 token endpoint. Supports authorization_code (PKCE verifier required), refresh_token (rotation + reuse detection), and client_credentials. Confidential clients authenticate with HTTP Basic or client_secret_post. Access tokens are RFC 9068 at+jwt, 1h TTL, audience-bound to the resource indicator. Subscription is re-checked on every issuance. Responses are no-store.
Authorizations
Confidential-client authentication at the token/revoke endpoints — HTTP Basic client_id:client_secret (or the equivalent client_secret_post body params). Public (PKCE) clients send only client_id and use no scheme.
Body
Form-encoded token request. Fields apply per grant_type: authorization_code uses code + redirect_uri + code_verifier; refresh_token uses refresh_token; client_credentials uses scope. Public clients also send client_id.
authorization_code, refresh_token, client_credentials PKCE verifier (authorization_code grant).
RFC 8707 resource indicator.
client_secret_post auth (alternative to HTTP Basic).
Response
Token issued.
RFC 6749 / 9068 token response.
RFC 9068 at+jwt
Bearer Seconds until expiry (3600).
Present when the client registered the refresh_token grant. The optional OIDC offline_access scope is not required.