This document covers an outdated version of the Auth0 authentication pipeline and the way scopes should be used. We recommend you use the latest version. For more on the latest authentication pipeline refer to Introducing OIDC Conformant Authentication.

When initiating a client-side authorization transaction through the /authorize endpoint, only an opaque Access Token will be returned by default. To also return a JWT that authenticates the user and contains their profile information, the scope parameter can be sent as part of the request.

Example (implicit flow)

The following URL logs a user in using Google and requests a JWT that authenticates the user.

After a successful transaction, the user would be redirected here:

When decoded, this token contains the following claims:

Requesting specific claims

The attributes included in the issued token can be controlled with the scope parameter as follows:

  • scope=openid: will only return iss, sub, aud, exp and iat claims.
  • scope=openid email nickname favorite_food: will return claims for openid in addition to the email, nickname and favorite_food fields if they are available.
  • scope=openid profile: will return all the user attributes in the token. Beware when you use this option because if you have too many user attributes the ID Token will increase in size and might break the URL limits for some browsers.

The scope parameter can be used in the same way when calling the Resource Owner endpoint.

Keep reading