IT Glossary

Refresh Token

A refresh token lets an OAuth client get new access tokens without signing in again. Why apps stay connected for months and why offboarding must revoke it.

November 2, 2026

What is a refresh token?

A refresh token is a credential that an OAuth 2.0 client uses to obtain new access tokens without asking the user to sign in again. RFC 6749 describes it as issued to the client by the authorization server and used when the current access token becomes invalid or expires. It usually lives far longer than an access token, which is why a third-party app can keep access for weeks or months after one consent.

Key takeaways

  • A refresh token lets an OAuth client obtain new access tokens without a new sign-in, which keeps an app's access alive for weeks or months.
  • A refresh token is presented only to the authorization server, never to the API, and lives much longer than the access tokens it produces.
  • RFC 9700 states that a refresh token issued to a public client must be sender-constrained or use refresh token rotation.
  • Disabling an account does not always revoke each refresh token already issued, so offboarding should revoke sessions and tokens explicitly.

How a refresh token works

  • Issuance: when a user approves an app, the authorization server can return a refresh token alongside the first access token, often because the app asked for offline access.
  • Storage: the client keeps the refresh token on its server or on the device, because without it the user has to sign in again.
  • Renewal: when the access token expires or becomes invalid, the client sends the refresh token to the authorization server and receives a new access token.
  • Rotation: with refresh token rotation, each renewal also returns a new refresh token and invalidates the previous one.
  • End of life: the token stops working when it expires, when the user or an admin revokes it, or when a provider policy ends it, which varies by provider.

Refresh token vs access token: which one keeps an app connected?

  • Access token: short-lived, presented to the API with every call, worthless once it expires.
  • Refresh token: long-lived, presented only to the authorization server, used to get new access tokens for as long as it stays valid.

The refresh token, not the access token, decides how long an app stays connected, which also makes it the more valuable credential to steal. RFC 9700, the OAuth 2.0 Security Best Current Practice published in January 2025, requires refresh tokens for public clients, such as mobile and single-page apps, to be sender-constrained or to use refresh token rotation.

Examples and use cases

A 120-person fintech offboards a product manager on a Friday. IT disables her Microsoft Entra ID account, which blocks new sign-ins. Over the year, she connected a roadmap tool, a scheduling app and a reporting add-on to her work account, and each of them holds a refresh token. Whether those tokens stop working depends on the provider and on each app: some are revoked with the account, others keep renewing access until they expire or someone revokes them. Her accounts inside those apps stay open either way.

Refresh tokens held by the apps a leaver used are a reason to deprovision in each app, not only in the identity provider. Corma's offboarding workflows remove accounts and access across SaaS apps, including those without SCIM, so HR and IT run the same departure checklist every time, alongside revoking sessions and tokens in the identity provider.

Related concepts

FAQ

How long does a refresh token last?

It depends on the provider and on the app's configuration. Some refresh tokens expire after a fixed period or after a period of inactivity, others stay valid until someone revokes them.

Does disabling a user revoke their refresh tokens?

Not always. Some identity providers and apps revoke refresh tokens when the account is disabled, others only block new sign-ins, so offboarding should revoke sessions and tokens explicitly.

What is refresh token rotation?

A mechanism in which each use of a refresh token returns a new one and invalidates the old one. A copy replayed after the legitimate app has renewed is refused.

Can an administrator revoke a refresh token?

Yes. Administrators can usually revoke a user's sessions and tokens, or remove an app's access, from the identity provider's admin console.

Request a demo