Application Settings Best Practices
Troubleshooting the Authorization Extension
The following are some issues you might see when setting up the Authorization Extension, as well as some tips to help you identify the cause.
Check the Client ID
The authentication results in a token that contains groups information, but not roles or permissions information.
If this happens, chances are that you created JSON Web Tokens (JWT)roles and permissions for one application, but your users are authenticating using another application. For example, let's say that you created all your roles/permissions against Website A. However, you also create another website application in Auth0 for Website B. Then, you use the
client_secret for Website B, instead of those for Website A, in your app.
Alternatively, you might see this if you click the Try button in the Auth0 Dashboard on a Connection that contains one of your users. This will execute an authentication flow using the Auth0 global application, but this is not the same as the application you configured in the extension.
Correct application type
The supported application types for the Authorization extension are: Native, Single-Page Web Applications and Regular Web Applications. Applications with no type assigned and Machine to Machine Applications are not supported.
Flag third-party applications
I upgraded to v2 and my users get an error upon login
If you see the error
You are not allowed to access this application, most probably there is some conflict with the old rule. Turn off the persistence settings, delete the existing rule, re-enable the settings, and test again.