{yourCallbackUrl}
. Your callback URL format will vary depending on your application type and platform. For details about the format for your application type and platform, see our Native/Mobile Quickstarts and Single-Page App Quickstarts.code_verifier
that will be sent to Auth0 to request tokens.code_challenge
from the code_verifier
that will be sent to Auth0 to request an authorization_code
.authorization_code
.authorization_code
and code_verifier
for tokens.code_verifier
, which is a cryptographically-random, Base64-encoded key that will eventually be sent to Auth0 to request tokens.
code_challenge
from the code_verifier
that will be sent to Auth0 to request an authorization_code
.
code_verifier
and the code_challenge
, you must get the user’s authorization. This is technically the beginning of the authorization flow, and this step may include one or more of the following processes:
code_challenge
you generated in the previous step and the method you used to generate the code_challenge
.
Parameter Name | Description |
---|---|
response_type | Denotes the kind of credential that Auth0 will return (code or token ). For this flow, the value must be code . |
code_challenge | Generated challenge from the code_verifier . |
code_challenge_method | Method used to generate the challenge (e.g., S256). The PKCE spec defines two methods, S256 and plain , the former is used in this example and is the only one supported by Auth0 since the latter is discouraged. |
client_id | Your application’s Client ID. You can find this value in your Application Settings. |
redirect_uri | The URL to which Auth0 will redirect the browser after authorization has been granted by the user. The Authorization Code will be available in the code URL parameter. You must specify this URL as a valid callback URL in your Application Settings. Warning: Per the OAuth 2.0 Specification, Auth0 removes everything after the hash and does not honor any fragments. |
scope | The scopes for which you want to request authorization. These must be separated by a space. You can request any of the standard OpenID Connect (OIDC) scopes about users, such as profile and email , custom claims conforming to a namespaced format, or any scopes supported by the target API (e.g., read:contacts ). Include offline_access to get a Refresh Token (make sure that the Allow Offline Access field is enabled in the Application Settings). |
audience | The unique identifier of the API your mobile app wants to access. Use the Identifier value on the Settings tab for the API you created as part of the prerequisites for this tutorial. |
state | (recommended) An opaque arbitrary alphanumeric string your app adds to the initial request that Auth0 includes when redirecting back to your application. To see how to use this value to prevent cross-site request forgery (CSRF) attacks, see Mitigate CSRF Attacks With State Parameters. |
organization | (optional) ID of the organization to use when authenticating a user. When not provided, if your application is configured to Display Organization Prompt, the user will be able to enter the organization name when authenticating. |
invitation | (optional) Ticket ID of the organization invitation. When inviting a member to an Organization, your application should handle invitation acceptance by forwarding the invitation and organization key-value pairs when the user accepts the invitation. |
HTTP 302
response. The authorization code is included at the end of the URL:
code
) from the previous step, you will need to POST
to the token URL sending along the code_verifier
.
Parameter Name | Description |
---|---|
grant_type | Set this to “authorization_code”. |
code_verifier | The cryptographically-random key that was generated in the first step of this tutorial. |
code | The authorization_code retrieved in the previous step of this tutorial. |
client_id | Your application’s Client ID. You can find this value in your Application Settings. |
redirect_uri | The valid callback URL set in your Application settings. This must exactly match the redirect_uri passed to the authorization URL in the previous step of this tutorial. Note that this must be URL encoded. |
access_token
, refresh_token
, id_token
, and token_type
values:
refresh_token
will only be present in the response if you included the offline_access
scope and enabled Allow Offline Access for your API in the Dashboard.
Refresh tokens must be stored securely since they allow a user to remain authenticated essentially forever.
offline_access
scope when you initiated the authentication request through the authorize endpoint.POST
request to the /oauth/token
endpoint in the Authentication API, using grant_type=refresh_token
.
Parameter Name | Description |
---|---|
grant_type | Set this to refresh_token . |
client_id | Your application’s Client ID. You can find this value in your Application Settings. |
refresh_token | The refresh token to use. |
scope | (optional) A space-delimited list of requested scope permissions. If not sent, the original scopes will be used; otherwise you can request a reduced set of scopes. Note that this must be URL encoded. |
HTTP 200
response with a payload containing a new access_token
, its lifetime in seconds (expires_in
), granted scope
values, and token_type
. If the scope of the initial token included openid
, then the response will also include a new id_token
: