{https://yourApp/callback}
. This field cannot be undefined or an error message will be returned.access_denied
error while testing the Password Owner Resource Grant, this could be due to an access control rule.
POST
to the token URL.
Parameter Name | Description |
---|---|
grant_type | Set this to password . |
username | The username entered by the user. |
password | The password entered by the user. |
client_id | Your application’s Client ID. You can find this value in your Application Settings. |
client_assertion | A JWT containing a signed assertion with your application credentials. Required when Private Key JWT is your application authentication method. |
client_assertion_type | The value is urn:ietf:params:oauth:client-assertion-type:jwt-bearer . Required when Private Key JWT is the application authentication method. |
client_secret | Your application’s Client Secret. Required when Client Secret is the application authentication method. Application Settings is Post or Basic . If your application is not highly trusted (for example, a SPA), then do not set this parameter. |
audience | The audience for the token, which is your API. You can find this in the Identifier field on your API’s settings tab. |
scope | Specifies the scopes for which you want to request authorization, which dictate which claims (or user attributes) you want returned. These must be separated by a space. You can request any of the standard OpenID Connect (OIDC) scopes about users, such as profile or email , custom claims conforming to a namespaced format, or any scopes supported by the target API (e.g., read:contacts ). Include offline_access to get a Refresh Token (make sure that the Allow Offline Access field is enabled in the Application Settings). |
HTTP 200
response with a payload containing access_token
, refresh_token
, id_token
, token_type
, and expires_in
values:
openid
scope in the request, all openid
standard OpenID Connect scopes will be returned. In these cases, the scope
parameter will be included in the response and will list the issued scopes.
openid
scope in your request. If the API uses RS256
as the signing algorithm, the Access Token will include /userinfo
as a valid audience, which means you can use it to invoke the /userinfo endpoint and retrieve the user’s claims.
offline_access
scope when you initiated the authentication request through the authorize endpoint.POST
request to the /oauth/token
endpoint in the Authentication API, using grant_type=refresh_token
.
Parameter Name | Description |
---|---|
grant_type | Set this to refresh_token . |
client_id | Your application’s Client ID. You can find this value in your Application Settings. |
refresh_token | The refresh token to use. |
scope | (optional) A space-delimited list of requested scope permissions. If not sent, the original scopes will be used; otherwise you can request a reduced set of scopes. Note that this must be URL encoded. |
HTTP 200
response with a payload containing a new access_token
, its lifetime in seconds (expires_in
), granted scope
values, and token_type
.
grant_type
request parameter to http://auth0.com/oauth/grant-type/password-realm
.realm
, and set it to the name of the realm to which the user belongs. For example, if you have configured a database connection for internal employees named employees
, and your user belongs to it, then set realm
to employees
.