Client authentication considerations at the OAuth 2.0 token endpoint

Client authentication considerations at the OAuth 2.0 token endpoint

The OAuth 2.0 token endpoint is used for direct communications between an OAuth client and the authorization server. The token endpoint is used to obtain an OAuth token. The client type, whether public or confidential, determines the authentication requirements of the OAuth 2.0 token endpoint. The Advanced Access Control runtime is responsible for authenticating the client using the client_id and client_secret in sending the request. OAuth 2.0 workflows for confidential clients that require client authentication at the token endpoint, can be configured in one of the following ways:

The Advanced Access Control point of contact requires authentication at the token endpoint:

The point of contact is responsible for authenticating the client.
The Confidential check box from the client instance panel is not relevant. A client_secret parameter must not be sent in the token endpoint request.
If a client_id parameter is sent in the request, it must match the identity of the client that is authenticated by the point of contact.

The Advanced Access Control point of contact permits unauthenticated access to the token endpoint:

The client_id parameter in the token endpoint request is used to identify the client.
The Confidential check box from the client instance panel determines whether a client_secret parameter is required in the token endpoint request. A client secret is required for confidential clients only.

Basic Authentication can be performed by the runtime instead of by the point of contact server.

When enforcing client authentication at the token endpoint, the point of contact must contain the client ID and client secret within its user registry. The point of contact must be able to map the authenticated user credential to the client_id parameter sent in the OAuth 2.0 token endpoint request. Based on this information, the following configurations are supported:

Client types Configurations WebSEAL point of contact token endpoint URI considerations Check box setting for the Confidential parameter

Confidential Point of contact performs client authentication.

Authenticated ACL on token endpoint is required.
Token endpoint port must match WebSEAL port.

N/A

Confidential Basic Authentication is performed by the runtime. Point of contact configuration does not need to make any change to the Authorization header. N/A

Confidential Client_id and client_secret parameters in the token endpoint request are used to perform client authentication.

Unauthenticated ACL on token endpoint is required.
Token endpoint port must match WebSEAL port.

Must be cleared.

Public Client_id parameter is used to perform client validation.

Unauthenticated ACL on token endpoint is required.
Token endpoint port must match the WebSEAL port.

Must be selected.

Parent topic: OAuth 2.0 and OIDC workflows

Client types	Configurations	WebSEAL point of contact token endpoint URI considerations	Check box setting for the Confidential parameter
Confidential	Point of contact performs client authentication.	Authenticated ACL on token endpoint is required. Token endpoint port must match WebSEAL port.	N/A
Confidential	Basic Authentication is performed by the runtime.	Point of contact configuration does not need to make any change to the Authorization header.	N/A
Confidential	Client_id and client_secret parameters in the token endpoint request are used to perform client authentication.	Unauthenticated ACL on token endpoint is required. Token endpoint port must match WebSEAL port.	Must be cleared.
Public	Client_id parameter is used to perform client validation.	Unauthenticated ACL on token endpoint is required. Token endpoint port must match the WebSEAL port.	Must be selected.