The client presents its authorization grant to the token endpoint to obtain an access token and a refresh token when needed.
The OAuth 2.0 Authorization Framework defines the token endpoint. Because the authorization endpoint directly issues an access token, every authorization grant uses this endpoint except the Implicit grant type.
This endpoint accepts only the HTTP POST method.
Parameters vary depending on the grant type. For more information, see OAuth grant type parameters. The required Content-Type value
Like other OAuth 2.0 endpoints, the token endpoint is accessible at the base URL and any configured virtual host names.
If the Token Endpoint Base URL field is configured on the Authorization Server Settings window ( ) the token endpoint is also accessible at that location.
For example, if the base URL is https://www.example.com:9031 and the Token Endpoint Base URL value is https://www.example.local:9031, the token endpoints are accessible at the following locations:
OAuth client identification and authentication
The authentication requirement of this endpoint depends on the client authentication method configured for the clients.
|Client secret||Clients can present their client identifier and client secret using the
HTTP Basic authentication scheme, where the client identifier is the
username, and the client secret is the password.
Clients can provide credentials using the request parameters client_id and client_secret.
This is a sensitive parameter. To avoid recording it in web server logs, only pass in this parameter with the HTTP POST method in the message body, or through the HTTP Basic authentication scheme.
|Client certificate||Clients must present their client certificate for mutual TLS authentication. The issuer and the subject distinguished name (DN) of the client certificate must match values configured for the clients.|
|Private key JWT||Clients must include request parameters
client_assertion in the message body of their requests.
For readability, line breaks are inserted and the authentication token is truncated.
For more information about the private_key_jwt client authentication method, see Client Authentication and Using Assertions for Client Authentication.
|None||Clients must pass in the client_id parameter in a query string or the message body to identify themselves.|
OAuth access token management parameters
PingFederate supports multiple access token management (ATM) instances. Clients can specify an ATM instance by providing the ATM ID (access_token_manager_id) or a resource URI (aud) in their requests to the PingFederate OAuth AS.
|access_token_manager_id||The access_token_manager_id value is the instance
ID of the desired ATM instance. When specified, PingFederate
uses the desired ATM instance for the request if it is eligible; otherwise
it aborts the request.
When the access_token_manager_id parameter is specified, PingFederate ignores the aud parameter.
|aud||The aud is the resource URI the client wants to access. The provided value is matched against resource URIs configured in access token management instances. When a match is found, PingFederate uses the corresponding access token management instance for the request if it is eligible; otherwise it aborts the request.|
A match can be an exact match or a partial match where the provided URI has the same scheme and authority parts and a more specific path contained within the path of the pre-configured resource URI. PingFederate takes an exact match over a partial match. If there are multiple partial matches, PingFederate takes the partial match where the provided URI matches more specifically against the pre-configured resource URI.
A partial matchA resource URI of
https://app.example.localis a partial match for the following provided URIs:
An exact match is a better match than a partial match
|Access Token Management instances||Resource URIs (configured)|
https://localhost:9031/app1 (a resource URI pre-configured for ATM1) is
a partial match for https://localhost:9031/app1/data (the provided URI). However,
PingFederate chooses ATM2 because
https://localhost:9031/app1/data (a resource URI pre-configured for
ATM2) is an exact match against the provided URI.
A more specific partial match is a better matchBoth
https://localhost:9031/app2/data(a resource URI for ATM1) and
https://localhost:9031/app2/data/get(a resource URI for ATM2) are partial matches for https://localhost:9031/app2/data/get/sample (the provided URI). However, PingFederate chooses ATM2 because
https://localhost:9031/app2/data/getmatches more specifically against the provided URI.