Protocols
Saved & recent

Refresh token

Also called: OAuth refresh token, refresh token rotation

A refresh token lets an OAuth client request fresh access tokens from the authorization server without repeating the full authorization interaction each time. It is not sent to the resource API. Issuing one is a policy choice, and its ability to prolong access makes its protection especially important.

For example, a calendar client exchanges refresh token R1 for a new access token. With rotation, the server also returns R2 and invalidates R1, retaining their relationship so reuse can reveal compromise. Current OAuth security guidance requires public-client deployments that issue refresh tokens to detect replay using rotation or sender-constrained tokens. Refreshing must remain within the authorization originally granted.

Read first
OAuth 2.0
Related
OAuth 2.0, Token revocation, Authorization code flow
Further reading
client authorization server calendar API refresh token R1 A2 + rotated R2 R1 invalidated access token A2 only client holds R2 API receives A2 example refresh-token rotation
In this refresh-token rotation example, R1 goes only to the authorization server. The client stores replacement R2 and uses the new access token A2 at the calendar API. R1 is invalidated.

View in the full Protocols collection