User consent and third-party applications
The OIDC-conformant authentication pipeline supports defining resource servers (such as APIs) as entities separate from applications. This lets you decouple APIs from the applications that consume them, and also lets you define third-party applications that you might not control or even fully trust.
Initiate a Silent Authentication request
Types of applications
All Auth0 applications are either first-party or third-party.
First-party applications are those controlled by the same organization or person that owns the Auth0 domain. For example, suppose you wanted to access the Contoso API; in this case, there would likely be a first-party application used for logging in at contoso.com.
Third-party applications are controlled by different people or organizations who most likely should not have administrative access to your Auth0 domain. They enable external parties or partners to access protected resources at your API in a secure way. A practical application of third-party applications is the creation of "developer centers", which allow users to obtain credentials in order to integrate their applications with your API. Similar functionality is provided by well-known APIs such as Facebook, Twitter, GitHub, and many others.
Successful authentication response
Creating a third-party application
All applications created from the management dashboard are assumed to be first-party by default.
At the time of writing, third-party applications cannot be created from the management dashboard.
They must be created through the management API, by setting
All applications created through Dynamic Client Registration will be third-party.
If a user is authenticating through a third-party application and is requesting authorization to access the user's information or perform some action at an API on their behalf, they will see a consent dialog. For example:
If the user allows the application, this creates a user grant which represents the user's consent to this combination of application, resource server, and OpenID Connect protocolscopes.
The application then receives a successful authentication response from Auth0 as usual. Once consent has been given, the user won't see the consent dialog during subsequent logins until consent is revoked explicitly.
Renew expired tokens
By default, the consent page will use the scopes' names to prompt for the user's consent. As shown below, you should define scopes using the action:resource_name format.
The consent page groups scopes for the same resource and displays all actions for that resource in a single line. For example, the configuration above would result in Posts: read and write your posts.
If you would like to display the Description field instead, you can do so by setting the tenant's use_scope_descriptions_for_consent to true. This will affect consent prompts for all of the APIs on that tenant.
To set the use_scope_descriptions_for_consent flag, you will need to make the appropriate call to the API:
Access Token expiration
Handling rejected permissions
If a user decides to reject consent to the application, they will be redirected to the
redirect_uri specified in the request with an
Skipping consent for first-party applications
Only first-party applications can skip the consent dialog, assuming the resource server they are trying to access on behalf of the user has the "Allow Skipping User Consent" option enabled.
Consent can't be skipped on localhost
Note that this option only allows verifiable first-party applications to skip consent at the moment. As
localhost is never a verifiable first-party (because any malicious application may run on
localhost for a user), Auth0 will always display the consent dialog for applications running on
localhost regardless of whether they are marked as first-party applications. During development, you can work around this by modifying your
/etc/hosts file to add an entry such as the following:
Similarly, you cannot skip consent (even for first-party applications) if
localhost appears in any domain in the callback URLAllowed Callback URLs setting (found in Dashboard > Applications > Settings). Make sure to update Allowed Callback URLs, and the callback URL you configured in your application, to match the updated domain-mapping.
Since third-party applications are assumed to be untrusted, they are not able to skip consent dialogs.
Polling with checkSession()
If a user has provided consent, but you would like to revoke it, you can do so via Dashboard > Users. Select the user in which you are interested, and switch over to the Authorized Applications tab.
Click Revoke next to the appropriate application.
When performing a Resource Owner Password Credentials exchange, there is no consent dialog involved. During a password exchange, the user provides their password to the application directly, which is equivalent to granting the application full access to the user's account.
Forcing users to provide consent
When redirecting to /authorize, the
prompt=consent parameter will force users to provide consent, even if they have an existing user grant for that application and requested scopes.
Customizing the consent dialog
The consent dialog UI cannot be customized or set to a custom domain.