Refresh token
A refresh token is a credential a client exchanges with an authorization server to obtain a new access token without repeating the user authorization process.
Spring in Action, Sixth Edition
A refresh token is a credential that a client presents to an authorization server to obtain a new access token after the current one expires.
- How it is used
- Uses refresh tokens to renew access to a secured ingredient API after access tokens expire.
- How deep it goes
- Shows client grant registration, a token response, and a curl refresh request.
- Examples
- Uses Taco Cloud’s ingredient API, a five-minute access token, and a curl request authenticated as taco-admin-client.
- What you can do after
- Apply it via curl to obtain a new access token and resume requests to a secured API.
Read how Spring in Action, Sixth Edition explains refresh token →
Software Security for Developers
A refresh token is a credential that a client presents to an authorization server to obtain a new access token without repeating the user authorization interaction.
- How it is used
- Maintains user sessions without repeated login prompts while limiting the exposure of short-lived access tokens.
- How deep it goes
- Explains registration, paired token issuance, renewal, and protection practices, but does not detail the token-exchange request mechanics.
- Examples
- Uses an ACME shopping session, token-endpoint responses, a five-minute expiry, and exercises about purpose, lifetime, and protection.
- What you can do after
- Operate session renewal by registering clients, handling refresh-token responses, and applying storage, rotation, expiration, and revocation safeguards.
Read how Software Security for Developers explains refresh token →
ASP.NET Core in Action, 3e
A refresh token is a credential that allows a client to obtain a new access token after the current access token expires without requiring the user to authenticate again.
- How it is used
- Supports continued API access after short-lived bearer tokens expire.
- How deep it goes
- Defines the exchange and security risk, but does not descend into implementation code.
- Examples
- Uses a five-minute access-token lifetime to illustrate renewal without another user login.
- What you can do after
- Apply it via OAuth or OpenID Connect to renew access without repeatedly authenticating the user.
Read how ASP.NET Core in Action, 3e explains refresh token →
Also covered in
What to know first
- authorization code flowThe authorization code flow is an OAuth authorization flow in which a client obtains a short-lived authorization code after authorization and exchanges it for tokens.
- OAuthOAuth is an authorization framework that enables a client to obtain limited, delegated access to protected resources without receiving the resource owner's credentials.
- Proof Key for Code ExchangeProof Key for Code Exchange (PKCE) is an OAuth security extension in which a client proves possession of a per-request secret when exchanging an authorization code.
Related concepts
- API keyproduces · An API key is a credential, usually represented as a string or token, presented with API requests to identify or authenticate a client and potentially authorize access.
- clientused by · A client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
- scopeconfigured by · Scope is a defined boundary that determines what entities, activities, resources, or conditions are included, governed, or permitted in a particular context.
- security tokenproduces · A security token is a credential or digitally verifiable assertion conveying identity or authority, used to authenticate requests or authorize access.
Questions about refresh token
What is refresh token?
A refresh token is a credential a client exchanges with an authorization server to obtain a new access token without repeating the user authorization process.
Which Manning books explain refresh token?
Spring in Action, Sixth Edition, Software Security for Developers and ASP.NET Core in Action, 3e.
What should I know before learning refresh token?
Manning books that teach refresh token usually introduce authorization code flow, OAuth, OAuth 2.1 and Proof Key for Code Exchange first.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


