Disable the Consent Screen for Profile When Logging Into Auth0 Applications

Overview

When users who are signing up or have been migrated from another database log in to Auth0 applications for the first time, a one-time authorization prompt appears. This occurs because only first-party applications bypass the consent dialog, and the target Application Programming Interface (API) requires administrators to enable the skip user consent option. Resolve this issue by enabling the skip user consent option for a Custom Application Programming Interface (API), or if the audience is the Management API, update the application to a first-party application.

Consent Screen 

 

Applies To

  • Auth0
  • Consent Screen for Profile
  • Auth0 Applications

Cause

Only first-party applications can skip the consent dialog, but only if the API they are trying to access on behalf of the user has the "Allow Skipping User Consent" option enabled.

Solution

How is the consent screen disabled?

The solution will depend on whether the audience is a Custom API or the Management API. Follow the steps or video below:

 

 

Audience is a Custom API

If the audience matches any Custom API from the tenant, the "Allow Skipping User Consent" option for that API can be enabled.

  1. From the left-hand menu within the Dashboard, navigate to Applications > API > {name-of-api}.
  2. Scroll down towards the bottom of the page until the "Allow Skipping User Consent" appears.
  3. Toggle this option to the green ( "on" ) position.

Allow Skipping User Consent Toggle Settings

 

Audience is the Management API

If the audience is the Management API, it is possible to determine whether an application is registered with Auth0 as a first-party or third-party application by making a call to the Get-a-Client endpoint.

curl --request GET \
  --url 'https://{yourDomain}/api/v2/clients/%7ByourClientId%7D?fields=is_first_party&include_fields=true' \
  --header 'authorization: Bearer {yourMgmtApiAccessToken}'

  1. Get an access token for use with the Management API.
  2. Call the Get-a-Client endpoint shown above, providing details of the Domain, Client_ID, and the Management API Access Token.
The outcome of this call will show either:
  • If the application is first-party, the is_first_party field will have a value of true.
  • If the application is third-party, the is_first_party field will have a value of false.

 

In a similar fashion, the is_first_party field can be updated by making a call to the Update-a-Client endpoint. 

 

Related References

Recommended content

No recommended content found...