You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2019. It is now read-only.
If the audience is set to YOUR_AUTH0_DOMAIN/userinfo, then the access token will be an opaque string.
If the audience is set to the unique identifier of a custom API, then the access token will be a JSON Web Token (JWT).
When the audience is set to a custom API and the scope parameter includes the openid value, then the generated access token will be a JWT valid for both retrieving the user's profile and for accessing the custom API. The audience parameter of this JWT will include two values: YOUR_AUTH0_DOMAIN/userinfo and your custom API's unique identifier.
Currently, in Doorman's codebase and documentation we only considered Access token opaque strings and JWT ID tokens. We should consider JWT Access tokens too.
The text was updated successfully, but these errors were encountered:
According to this:
https://auth0.com/docs/tokens/access-token#access-token-format
Currently, in Doorman's codebase and documentation we only considered Access token opaque strings and JWT ID tokens. We should consider JWT Access tokens too.
The text was updated successfully, but these errors were encountered: