Overview#
Token_endpoint is the OAuth 2.0 Endpoint on the Authorization Server where the OAuth Client exchanges the Authorization Grant, client_id and Client Secret, for an Access Token by submission of Access Token Request. To obtain an Access Token, an OpenID Connect Identity Token, and optionally a Refresh Token, the OAuth Client sends a Token Request to the Token_endpoint to obtain a Access Token Response, as described in Section 3.2 of OAuth 2.0 RFC 6749, when using the Authorization Code Flow.Communication with the Token_endpoint MUST utilize TLS.
More Information#
There might be more information for this subject on one of the following:- Access Token
- Access Token Request
- Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants
- Authorization API
- Authorization Code
- Authorization Code Flow
- Authorization Cross Domain Code 1.0
- Authorization Server
- Client Authentication Methods
- Client Credentials Grant
- Code_challenge_method
- Explicit Endpoint
- Grant Types
- Hybrid Flow
- Implicit Grant
- JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants
- Mutual TLS Profiles for OAuth Clients
- Mutual TLS Sender Constrained Resources Access
- OAuth 2.0 Endpoints
- OAuth 2.0 Token Exchange
- OAuth 2.0 Token Exchange Request
- OAuth Parameters Registry
- OAuth Scopes
- OAuth Token Request
- OpenAM Endpoints
- OpenID Connect
- Openid-configuration
- Permission ticket
- Proof Key for Code Exchange by OAuth Public Clients
- Protection API
- Refresh Token
- Resource Owner Password Credentials Grant
- Resource Parameter
- Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization Grants
- Token_endpoint_auth_method
- Token_endpoint_auth_methods_supported
- Token_endpoint_auth_signing_alg_values_supported
- Uma-configuration
