> For the complete documentation index, see [llms.txt](/docs/llms.txt) # Manage Software Tokens | FusionAuth Docs Learn about OAuth2 and OpenID Connect Tokens and how they are used. # Manage Software Tokens When using the OAuth2 and OpenID Connect authentication grants you'll be dealing with some tokens. We'll review each token type, the purpose and how to use them. Here's a presentation discussing how to use JWTs in a microservices architecture: [Play](https://youtube.com/watch?v=SLc3cTlypwM) ## JWT Structure[#](#jwt-structure) With the exception of the refresh token, each token described here is a JSON Web Token (JWT) and each JWT has a header, a payload and a signature. You can [decode JWTs using any number of online tools](/dev-tools/jwt-decoder), because it's two base 64 encoded strings joined by periods, with the signature for integrity checking. ![The components of a JWT.](/img/shared/json-web-token.png) ## Header[#](#header) The following describes the claims found in the JWT header. `gty`ArrayAvailable since 1.36.0DEPRECATED The list of grant types in chronological order. For example, if the token was the result of an `authorization_code` grant, the value will be `[authorization_code]`. If the token was generated using a refresh token using the `refresh_token` grant, the value will be `[authorization_code, refresh_token]` if the initial grant used to obtain the refresh token was the `authorization_code` grant. Removed in 1.160.0 As of version `1.60.0`, this claim is no longer returned in the header. This claim has moved to the JWT body. `kid`String The unique key identifier that represents the key used to build the signature. `typ`String The type of token, this value is always `JWT`. ## Access Token[#](#access-token) The access token is an opaque token per the OAuth2 specification. In the FusionAuth implementation the access token is a JSON Web Token (JWT). ### Access Token Claims[#](#access-token-claims) `applicationId`UUID The unique Id of the Application for which the user has been authenticated. This claim is only present if the user is registered for the application. `aud`String The audience the JWT is intended for. This registered claim is defined by [RFC 7519 Section 4.1.3](https://tools.ietf.org/html/rfc7519#section-4.1.3). This claim will be equal to the `client_id`, or, if one or more `resource` values was provided, an array containing both the `client_id` and the list of resources. `authenticationType`String The method used to authenticate the user that resulted in the generated JWT. The possible values are: * `APPLE` - The user was authenticated using Apple. Available since 1.17.0 * `APPLICATION_TOKEN` - The user was authenticated using an Application Authentication Token. * `EpicGames` - The user was authenticated using Epic Games. Available since 1.28.0 * `FACEBOOK` - The user was authenticated using Facebook. Available since 1.1.0 * `FEDERATED_JWT` - The user was authenticated using a JWT from an external source. * `GENERIC_CONNECTOR` - The user was authenticated using a generic connector. Available since 1.18.0 * `GOOGLE` - The user was authenticated using Google. Available since 1.1.0 * `HYPR` - The user was authenticated using HYPR. Available since 1.12.0 * `JWT_SSO` - A valid JWT associated with one application was exchanged for another JWT associated with a different application. * `LDAP_CONNECTOR` - The user was authenticated using an LDAP connector. Available since 1.18.0 * `LINKEDIN` - The user was authenticated using LinkedIn. Available since 1.23.0 * `Nintendo` - The user was authenticated using Nintendo. Available since 1.36.0 * `ONE_TIME_PASSWORD` - The user was authenticated using a one-time password. Available since 1.5.0 * `OPENID_CONNECT` - The user was authenticated using OIDC. Available since 1.1.0 * `PASSWORD` - The user was authenticated using a loginId and password combination. * `PASSWORDLESS` - The user was authenticated using a passwordless login link. Available since 1.5.0 * `PING` - The user was authenticated using a `PUT` request on the Login API. This is used to record a login event without prompting for credentials, such as when the FusionAuth SSO session is used. * `REFRESH_TOKEN` - The user requested a new JWT using a refresh token. * `REGISTRATION` - The user was created using the Registration API. Available since 1.16.0 * `SAMLv2` - The user was authenticated using SAMLv2. Available since 1.6.0 * `SAMLv2IdpInitiated` - The user was authenticated using SAMLv2 IdP Initiated login. Available since 1.28.0 * `SonyPSN` - The user was authenticated using Sony. Available since 1.28.0 * `Steam` - The user was authenticated using Steam. Available since 1.28.0 * `TWITTER` - The user was authenticated using Twitter. Available since 1.1.0 * `Twitch` - The user was authenticated using Twitch. Available since 1.28.0 * `USER_CREATE` - The user was created using the User API. Available since 1.16.0 * `WebAuthn` - The user was authenticated using a passkey. Available since 1.41.0 * `Xbox` - The user was authenticated using Xbox. Available since 1.28.0 `auth_time`LongAvailable since 1.36.0 The time of the initial authentication request, expressed as [unix time](/docs/reference/data-types#unix-time). The value will not change even if the token is re-issued using a Refresh Token. `email`String The email address of the user whose claims are represented by this JWT. Removed in 1.50.0 In version `1.50.0` and later this claim is not returned when the **oauthConfiguration.scopeHandlingPolicy** value of the Application is `Strict`. `email_verified`Boolean The verification status of the **email**. This value is `true` when the email is verified. Removed in 1.50.0 In version `1.50.0` and later this claim is not returned when the **oauthConfiguration.scopeHandlingPolicy** value of the Application is `Strict`. `exp`Long The expiration instant of the JWT, expressed as [unix time](/docs/reference/data-types#unix-time). This registered claim is defined by [RFC 7519 Section 4.1.4](https://tools.ietf.org/html/rfc7519#section-4.1.4). `gty`ArrayAvailable since 1.60.0 The list of grant types in chronological order. For example, if the token was the result of an `authorization_code` grant, the value will be `[authorization_code]`. If the token was generated using a refresh token using the `refresh_token` grant, the value will be `[authorization_code, refresh_token]` if the initial grant used to obtain the refresh token was the `authorization_code` grant. This claim is will not be present if the token was generated outside of an OAuth grant. `iat`Long The instant that the JWT was issued, expressed as [unix time](/docs/reference/data-types#unix-time). This registered claim is defined by [RFC 7519 Section 4.1.6](https://tools.ietf.org/html/rfc7519#section-4.1.6). `jti`StringAvailable since 1.18.0 The unique identifier for this JWT. This registered claim is defined by [RFC 7519 Section 4.1.7](https://tools.ietf.org/html/rfc7519#section-4.1.7). `iss`String The issuer of the JWT. For FusionAuth, this is always the value defined in the tenant JWT configuration. This registered claim is defined by [RFC 7519 Section 4.1.1](https://tools.ietf.org/html/rfc7519#section-4.1.1). `preferred_username`StringAvailable since 1.5.0 The username of the user whose claims are represented by this JWT. Removed in 1.50.0 In version `1.50.0` and later this claim is not returned when the **oauthConfiguration.scopeHandlingPolicy** value of the Application is `Strict`. `roles`Array The roles assigned to the user in the authenticated Application. This claim is only present if the user is registered for the Application. `scope`StringAvailable since 1.50.0 The scope of the Access token. This meaning of this field is specified by [RFC 6749 Section 3.3](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). Contains the validated and consented OAuth scopes from the initial authentication request. See [Scopes](/docs/lifecycle/authenticate-users/oauth/scopes) for more detail on scope consent. `sid`StringAvailable since 1.37.0 The unique Id of the refresh token returned along with this access token when the `offline_access` scope was requested. This unique Id is the persistent identifier for this refresh token, and will not change even when using one-time use refresh tokens. This value may optionally be used to revoke the token using the [Refresh Token API](/docs/apis/jwt/revoke-refresh-tokens). `sub`UUID The subject of the token. The value is the unique Id of the FusionAuth user. This registered claim is defined by [RFC 7519 Section 4.1.2](https://tools.ietf.org/html/rfc7519#section-4.1.2). `tid`UUIDAvailable since 1.36.0 The FusionAuth Tenant unique Id. `tty`UUIDAvailable since 1.60.0 The token type. This value will always be `at` indicating this is an `access token`. ### Sample Access Token[#](#sample-access-token) Here's a sample access token. ``` eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImd0eSI6WyJhdXRob3JpemF0aW9uX2NvZGUiXSwia2lkIjoiWG9xN2tLM2VJWHJ5WW1pNTBaT3ZnMmJjY2VNIn0.eyJhdWQiOiJlOWZkYjk4NS05MTczLTRlMDEtOWQ3My1hYzJkNjBkMWRjOGUiLCJleHAiOjE3MDMwMzcxODAsImlhdCI6MTcwMzAzMzU4MCwiaXNzIjoiYWNtZS5jb20iLCJzdWIiOiIwMDAwMDAwMC0wMDAwLTAwMDAtMDAwMC0xMTExMTExMTExMTEiLCJqdGkiOiIyZTIyNzFkNy0zMDU3LTRiZmQtOTlhYi0zNGFmNDhlODQ1NjciLCJhdXRoZW50aWNhdGlvblR5cGUiOiJQQVNTV09SRCIsImVtYWlsIjoicmljaGFyZEBleGFtcGxlLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJhcHBsaWNhdGlvbklkIjoiZTlmZGI5ODUtOTE3My00ZTAxLTlkNzMtYWMyZDYwZDFkYzhlIiwic2NvcGUiOiJvZmZsaW5lX2FjY2VzcyBwcm9maWxlIG9wZW5pZCIsInJvbGVzIjpbXSwic2lkIjoiMGFiZTcxMzktMGJkMC00ZmQwLWE0NTAtYzFlOGIxNmU3MTBhIiwiYXV0aF90aW1lIjoxNzAzMDMzNTgwLCJ0aWQiOiJkN2QwOTUxMy1hM2Y1LTQwMWMtOTY4NS0zNGFiNmM1NTI0NTMifQ.IyQL-d2BgG0VmfHg2gmge7MgDwYXrMX7xDv5lz-pe0oravlZUAt0B9DhfPaY-EFZ0Dus95dTIVtU4-THYkGNy4Un21FjoTAGU8fZK_Cew16814194WvQDR5wL_cZymog9UmmUv_owKot5YzwLdoJKXVBI7CgM3c43KrwGOdFPMHNkL-YHQgWFQzXBfRpmdu45K56Np8mYVbgVwFKgRXRIGy0PpBGaoeRiN1DfeB3fzR944ddActyOfTVovIXqO7O5HORS8vFQA6h1wpNdAtrbCMqHEVgQWHSMZCkUGM7RlE3V9WepRcaLkpuMocQfxDasoRZCIeK1ZwRHuSbAh7zFA ``` ## Client Credentials Access Token[#](#client-credentials-access-token) The access token is an opaque token per the OAuth2 specification. In the FusionAuth implementation, the credentials access token is a JSON Web Token (JWT). Available since version 1.26. ### Client Credentials Access Token Claims[#](#client-credentials-access-token-claims) `aud`Array The audience(s) of this token. This value is equal to the target Entity's unique Id in FusionAuth. This registered claim is defined by [RFC 7519 Section 4.1.3](https://tools.ietf.org/html/rfc7519#section-4.1.3). Note that prior to version `1.60.0`, this claim was a string when a single entity was defined in the scope using `target-entity:` and an array when more than one entity was defined in the scope. To simplify integrations, this claim is now always returned as an array. `exp`Long The expiration instant of the JWT expressed as [unix time](/docs/reference/data-types#unix-time). This registered claim is defined by [RFC 7519 Section 4.1.4](https://tools.ietf.org/html/rfc7519#section-4.1.4). `gty`ArrayAvailable since 1.60.0 The list of grant types in chronological order. For example, if the token was the result of an `authorization_code` grant, the value will be `[authorization_code]`. If the token was generated using a refresh token using the `refresh_token` grant, the value will be `[authorization_code, refresh_token]` if the initial grant used to obtain the refresh token was the `authorization_code` grant. `iat`Long The instant that the JWT was issued expressed as [unix time](/docs/reference/data-types#unix-time). This registered claim is defined by [RFC 7519 Section 4.1.6](https://tools.ietf.org/html/rfc7519#section-4.1.6). `iss`String The issuer of the JWT. For FusionAuth, this is always the value defined in the tenant JWT configuration. This registered claim is defined by [RFC 7519 Section 4.1.1](https://tools.ietf.org/html/rfc7519#section-4.1.1). `jti`String The unique identifier for this JWT. This registered claim is defined by [RFC 7519 Section 4.1.7](https://tools.ietf.org/html/rfc7519#section-4.1.7). `permissions`Array The permission granted to the recipient Entity by the target Entity. This claim is only present if permissions are associated with the grant and any requested permissions are found in the grant. `scope`String The scope of the Access token. This meaning of this field is specified by [RFC 6749 Section 3.3](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3) and referenced in Client Credentials Grant [RFC 6749 Section 4.4](https://datatracker.ietf.org/doc/html/rfc6749#section-4.4) Valid scopes are described in the [client credentials scopes section](/docs/lifecycle/authenticate-users/oauth/#client-credentials-scopes). `sub`UUID The subject of the token. The value is the unique Id of the recipient Entity. This registered claim is defined by [RFC 7519 Section 4.1.2](https://tools.ietf.org/html/rfc7519#section-4.1.2). `tid`UUIDAvailable since 1.36.0 The unique Id of the user's tenant. `tty`UUIDAvailable since 1.60.0 The token type. This value will always be `at` indicating this is an `access token`. `use`StringAvailable since 1.60.0 The intended use for this token. This claim will only be present when an access token has been created for use by the FusionAuth SCIM server. When the claim is present the value will be `scim_server`. ## Id Token[#](#id-token) The Id Token is part of the OpenID Connect specification. The Id Token is a JSON Web Token (JWT) per the OpenID Connect specification. The Id Token is similar to the access token in the FusionAuth implementation. The Id Token may contain additional claims not present in the Access Token. The Id Token may be returned as part of an Authentication request when the `openid` scope is requested. In version `1.50.0` and later the Id Token claims are populated based on the requested OAuth scopes when the **oauthConfiguration.scopeHandlingPolicy** value of the application object is `Strict`. ### Id Token Claims[#](#id-token-claims) `applicationId`UUID The unique Id of the Application for which the user has been authenticated. This claim is only present if the user is registered for the application. Removed in 1.24.0 As of version `1.24.0`, this claim is no longer returned by default. The `id_token` should not be utilized for authorization, so this claim was removed to make it less likely for a holder of this token to incorrectly utilize this token. If you have a need for this claim, it can be added back using a JWT populate lambda. `at_hash`StringAvailable since 1.5.0 The Access Token hash value. As defined by the [3.1.3.6 of the OpenID Connect Core specification](https://openid.net/specs/openid-connect-core-1_0.html#CodeIDToken) this value is a base64 encoded hash of the access token. `aud`String The audience the JWT is intended for. This registered claim is defined by [RFC 7519 Section 4.1.3](https://tools.ietf.org/html/rfc7519#section-4.1.3). This claim will be equal to the `client_id`, or, if one or more `resource` values was provided, an array containing both the `client_id` and the list of resources. `authenticationType`String The method used to authenticate the user that resulted in the generated JWT. The possible values are: * `APPLE` - The user was authenticated using Apple. Available since 1.17.0 * `APPLICATION_TOKEN` - The user was authenticated using an Application Authentication Token. * `EpicGames` - The user was authenticated using Epic Games. Available since 1.28.0 * `FACEBOOK` - The user was authenticated using Facebook. Available since 1.1.0 * `FEDERATED_JWT` - The user was authenticated using a JWT from an external source. * `GENERIC_CONNECTOR` - The user was authenticated using a generic connector. Available since 1.18.0 * `GOOGLE` - The user was authenticated using Google. Available since 1.1.0 * `HYPR` - The user was authenticated using HYPR. Available since 1.12.0 * `JWT_SSO` - A valid JWT associated with one application was exchanged for another JWT associated with a different application. * `LDAP_CONNECTOR` - The user was authenticated using an LDAP connector. Available since 1.18.0 * `LINKEDIN` - The user was authenticated using LinkedIn. Available since 1.23.0 * `Nintendo` - The user was authenticated using Nintendo. Available since 1.36.0 * `ONE_TIME_PASSWORD` - The user was authenticated using a one-time password. Available since 1.5.0 * `OPENID_CONNECT` - The user was authenticated using OIDC. Available since 1.1.0 * `PASSWORD` - The user was authenticated using a loginId and password combination. * `PASSWORDLESS` - The user was authenticated using a passwordless login link. Available since 1.5.0 * `PING` - The user was authenticated using a `PUT` request on the Login API. This is used to record a login event without prompting for credentials, such as when the FusionAuth SSO session is used. * `REFRESH_TOKEN` - The user requested a new JWT using a refresh token. * `REGISTRATION` - The user was created using the Registration API. Available since 1.16.0 * `SAMLv2` - The user was authenticated using SAMLv2. Available since 1.6.0 * `SAMLv2IdpInitiated` - The user was authenticated using SAMLv2 IdP Initiated login. Available since 1.28.0 * `SonyPSN` - The user was authenticated using Sony. Available since 1.28.0 * `Steam` - The user was authenticated using Steam. Available since 1.28.0 * `TWITTER` - The user was authenticated using Twitter. Available since 1.1.0 * `Twitch` - The user was authenticated using Twitch. Available since 1.28.0 * `USER_CREATE` - The user was created using the User API. Available since 1.16.0 * `WebAuthn` - The user was authenticated using a passkey. Available since 1.41.0 * `Xbox` - The user was authenticated using Xbox. Available since 1.28.0 `auth_time`LongAvailable since 1.36.0 The time of the initial authentication request expressed as [unix time](/docs/reference/data-types#unix-time). The value will not change even if the token is re-issued using a Refresh Token. `birthdate`StringAvailable since 1.50.0 The birthDate of the user if available. Format will be in `YYYY-MM-DD` as defined by the OpenID Connect core specification. When the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `c_hash`StringAvailable since 1.5.0 The Authorization Code hash value. As defined by the [3.3.2.11 of the OpenID Connect Core specification](https://openid.net/specs/openid-connect-core-1_0.html#HybridIDToken) this value is an encoded hash of the authorization code, the algorithm used to generate this hash depends upon the algorithm used to generate the `id_token` signature. `email`String The email address of the user whose claims are represented by this JWT. In version `1.50.0` and later, when the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `email` scope. `email_verified`Boolean The verification status of the **email**. This value is `true` when the email is verified. In version `1.50.0` and later, when the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `email` scope. `exp`Long The expiration instant of the JWT, expressed as [unix time](/docs/reference/data-types#unix-time). This registered claim is defined by [RFC 7519 Section 4.1.4](https://tools.ietf.org/html/rfc7519#section-4.1.4). `family_name`StringAvailable since 1.50.0 The last name of the user if available. When the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `given_name`StringAvailable since 1.50.0 The first name of the user if available. When the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `gty`ArrayAvailable since 1.60.0 The list of grant types in chronological order. For example, if the token was the result of an `authorization_code` grant, the value will be `[authorization_code]`. If the token was generated using a refresh token using the `refresh_token` grant, the value will be `[authorization_code, refresh_token]` if the initial grant used to obtain the refresh token was the `authorization_code` grant. `iat`Long The instant that the JWT was issued, expressed [unix time](/docs/reference/data-types#unix-time). This registered claim is defined by [RFC 7519 Section 4.1.6](https://tools.ietf.org/html/rfc7519#section-4.1.6). `iss`String The issuer of the JWT. For FusionAuth, this is always the value defined in the tenant JWT configuration. This registered claim is defined by [RFC 7519 Section 4.1.1](https://tools.ietf.org/html/rfc7519#section-4.1.1). `jti`StringAvailable since 1.18.0 The unique identifier for this JWT. This registered claim is defined by [RFC 7519 Section 4.1.7](https://tools.ietf.org/html/rfc7519#section-4.1.7). `middle_name`StringAvailable since 1.50.0 The middle name of the user if available. When the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `name`StringAvailable since 1.50.0 The full name of the user if available. When the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `nonce`StringAvailable since 1.5.0 `phone_number`StringAvailable since 1.50.0 The phone number of the user if available. (**user.phoneNumber** or **user.mobilePhone** will be used in this order of precedence). This field is only populated when the `Scope handling policy` is `Strict`, and the **scope** claim contains the `phone` scope. `phone_number_verified`BooleanAvailable since 1.59.0 The verification status of the **phone\_number**. This value is `true` when the phone number is verified. This claim is based only on the **user.phoneNumber** verification status. This field is only populated when the `Scope handling policy` is `Strict`, and the **scope** claim contains the `phone` scope. `picture`StringAvailable since 1.50.0 A URL to a picture of the user if available. When the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `preferred_username`StringAvailable since 1.5.0 The username of the user whose claims are represented by this JWT. In version `1.50.0` and later, when the `Scope handling policy` is `Strict`, this field is only populated when the **scope** claim contains the `profile` scope. `roles`ArrayDEPRECATED The roles assigned to the user in the authenticated Application. This claim is only present if the user is registered for the application. Removed in 1.24.0 As of version `1.24.0`, this claim is no longer returned by default. The `id_token` should not be utilized for authorization, so this claim was removed to make it less likely for a holder of this token to incorrectly utilize this token. If you have a need for this claim, it can be added back using a JWT populate lambda. `scope`StringAvailable since 1.50.0 The scope of the Id Token. This meaning of this field is specified by [RFC 6749 Section 3.3](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). Contains the validated and consented OAuth scopes from the initial authentication request. See [Scopes](/docs/lifecycle/authenticate-users/oauth/scopes) for more detail on scope consent. `sid`String The SSO session Id. This claim will only be present when this token is produced using an interactive grant during a single-signon request such as the Authorization Code grant or the `Implicit` grant. `sub`UUID The subject of the token. The value is the unique Id of the FusionAuth user. This registered claim is defined by [RFC 7519 Section 4.1.2](https://tools.ietf.org/html/rfc7519#section-4.1.2). `tid`UUIDAvailable since 1.36.0 The unique Id of the user's tenant. `tty`UUIDAvailable since 1.60.0 The token type. This value will always be `idt` indicating this is an `id_token`. ### Sample Id Token[#](#sample-id-token) Here's a sample Id token. ``` eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImd0eSI6WyJhdXRob3JpemF0aW9uX2NvZGUiXSwia2lkIjoiWG9xN2tLM2VJWHJ5WW1pNTBaT3ZnMmJjY2VNIn0.eyJhdWQiOiJlOWZkYjk4NS05MTczLTRlMDEtOWQ3My1hYzJkNjBkMWRjOGUiLCJleHAiOjE3MDMwMzcxODAsImlhdCI6MTcwMzAzMzU4MCwiaXNzIjoiYWNtZS5jb20iLCJzdWIiOiIwMDAwMDAwMC0wMDAwLTAwMDAtMDAwMC0xMTExMTExMTExMTEiLCJqdGkiOiIyOWVkMjA5NC1jOWIxLTRmMGQtODc4Mi00YTc2NWI4YTZmOTIiLCJhdXRoZW50aWNhdGlvblR5cGUiOiJQQVNTV09SRCIsImVtYWlsIjoicmljaGFyZEBleGFtcGxlLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJhdF9oYXNoIjoiZmtqUzc4YjhCbXRlM2lRRVBIRUk2ZyIsImNfaGFzaCI6ImlrT3lkdmljUHRqNU9HMm5zcExtOFEiLCJzY29wZSI6Im9mZmxpbmVfYWNjZXNzIHByb2ZpbGUgb3BlbmlkIiwic2lkIjoiNjlhOTQ4OTYtNjg3ZS00MDQ5LTkwZGItMTY0ZDYwYWVmN2I2IiwiYXV0aF90aW1lIjoxNzAzMDMzNTgwLCJ0aWQiOiJkN2QwOTUxMy1hM2Y1LTQwMWMtOTY4NS0zNGFiNmM1NTI0NTMifQ.rT7Q39-RFT63aw996v0zu2vwS-RIYRvTccmEi_rGV19aKnRnlZD7Bx_dJaaoZxyvD3xfO1wVA2aO_nHQmKhwLuFIt4Jae0Z4a3nlJLKaumCxh4yB4vjAvKAwvhClwWYhx1LbbMl0lvVy-qvs-niVTgPLTVMYnSFXnfTuN8LMDCf7keP3SjS1MTyEeG2WtZzvPd6j2zu66rl5y3uCfpqaLbR0URDsJjQE4GbUMf7UODhZ1_ztGXg_-vGKvpomGB0-0vUmcrqXENtXRFy9hPYHXGp4T-uAy93DUo7AvsrECAHryWq6wzbLIXXeMcCpjWl87Cqb0TwMyM5D30VH2crlLQ ``` ## Refresh Token[#](#refresh-token) The refresh token is an opaque token that is used to "refresh", or obtain a new access token. Because the life of an access token is generally measured in minutes, the Refresh Token is by comparison a long lived token that can be used to maintain access to a protected resource. A refresh token is associated with the same set of validated and consented OAuth scopes from the initial authentication request. The [Refresh Token Grant Request](/docs/apis/oauth/token#refresh-token-grant-request) can include a subset of the original scopes to request a new token with a narrower scope. To request a refresh token during authentication you must provide the `offline_access` scope. The refresh token is not supported by the Implicit Grant, so if you provide the `offline_access` scope during an Implicit Grant workflow it will be ignored. If you request the `offline_access` scope and an Refresh Token is not returned, ensure that the FusionAuth application has been configured to generate refresh tokens. Ensure `Generate refresh tokens` is enabled in your application settings. See Settings -> Applications -> OAuth . This setting will cause a Refresh Token to be returned when the `offline_access` scope is requested. You will also want to ensure the `Refresh Token` grant is enabled which allows the use of the Refresh Token to be exchanged for a new Access Token. ### Sample Refresh Token[#](#sample-refresh-token) Here's a sample refresh token. ``` ze9fi6Y9sMSf3yWp3aaO2w7AMav2MFdiMIi2GObrAi-i3248oo0jTQ ```