Auth0
and RFC 9068
. To read more about the difference between the two profiles, read Access Token Profiles.
token_dialect
parameter for an API using the Management API.
The following code sample makes a PATCH request to the Update a resource server endpoint:
API_ID
, MGMT_API_ACCESS_TOKEN
, and TOKEN_DIALECT
with their respective values, as described in the following table:
Parameter | Description |
---|---|
API_ID | ID of the API for which you want to update the token dialect. |
MGMT_API_ACCESS_TOKEN | Access Token for the Management API with the scope update:resource_servers . |
TOKEN_DIALECT | Dialect of the access token for the specified API. To learn more, read Token dialect options. |
Value | Description |
---|---|
access_token | The default Auth0 token profile generates an access token formatted as a JSON Web Token (JWT). To learn more, read Access Token Profiles. |
access_token_authz | The default Auth0 token profile (access_token ) with the permissions claim. To learn more about RBAC permissions, read Enable Role-Based Access Control for APIs. |
rfc9068_profile | The RFC 9068 token profile generates an access token formatted as a JWT following the IETF JWT Profile for OAuth 2.0 Access Tokens (RFC 9068). To learn more, read Access Token Profiles. |
rfc9068_profile_authz | The RFC 9068 profile (rfc9068_profile ) with the permissions claim. To learn more about RBAC permissions, read Enable Role-Based Access Control for APIs. |