Authorization Extension's GET /users endpoint returns Internal Server Error (500)

Archived
,
3

As you mentioned the cause of the error is clear (incorrect credentials), but the reason for the extension to get into that situation may be more elusive.

In your situation here’s a few things I would try given that you already mentioned that re-installing the extension is feasible.

First:

  1. uninstall the extension.
  2. ensure that there is no client application named auth0-authz; if there is one and you’re confident that it’s not being used for anything else besides the extension, delete it.
  3. install the extension.
  4. open the browser tools and go to the network tab.
  5. click the settings button for the extension and in the network tab select the GET request to /adf6e2f2b84784b57522e3b19dfc9201?decrypt=true.
  6. in the preview section expand the secret and take note of the value associated with AUTH0_CLIENT_ID.
  7. go to the application section and check the client identifier associated with the auth0-authz application that should have been newly created by the extension install process.

If both client identifier match complete the same process that previously was leading to the error; if the error persists then sharing the following information may be useful:

  • the full URL to the /adf6e2f2b84784b57522e3b19dfc9201?decrypt=true request you inspected.
  • the full URL used to access the extension through the dashboard.
  • the full URL used in direct (HTTP) calls that are performed to the extension API (for example, from rules or from your own HTTP clients).

Sharing the URL will disclose the exact tenant name so you may replace the tenant name with a placeholder, however, be consistent and replace it the same placeholder in all shared URL’s. Also, only replace the tenant name and not the full domain name.