Access Token Caching
The concept name is missing or undefined, and the provided sources do not contain enough retrievable content to ground a complete, accurate definition. Please supply a valid concept name and ensure the source snippets include sufficient detail to support a definition.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept OAuth2 Client Credentials Grant Flow The provided sources do not contain sufficient information to define a specific, identifiable SAP developer concept — the concept name is listed as "undefined" and the source snippets cover a broad range of unrelated topics (OAuth2 Proxy, JWT security, API calls, service instances, and various tutorials) without converging on a single definable concept. A meaningful, source-grounded definition cannot be produced.
- Concept JSON File-Based Token Persistence A **refresh token** is a long-lived credential used in OAuth 2.0 flows that allows a developer to obtain new bearer tokens without requiring the user to re-authenticate. Developers use it to automate token lifecycle management, ensuring uninterrupted access to Concur APIs by programmatically replacing expiring access tokens. It is typically acquired alongside a bearer token during the initial token creation process and managed through refresh token automation workflows.
- Concept OAuth2 Token Flow (Refresh and Access Tokens) The concept name was not provided (received "undefined"), so a grounded definition cannot be written. Please supply a valid concept name so that a definition can be authored from the available source snippets.