Client authentication schemes
Most OAuth and OpenID Connect use cases require the client application to authenticate successfully before its requests can be processed further.
As an OAuth authorization server (OAuth AS), PingFederate supports the following client authentication schemes:
-
Client secret for HTTP Basic authentication
-
Client TLS certificate for mutual TLS authentication
-
Private key JWT for the private_key_jwt client authentication method, as defined in the OpenID Connect specification
-
Client secret JWT for the client_secret_jwt client authentication method, as defined in the OpenID Connect specification
-
None when authentication is not required
|
An OAuth client can be configured with one or more of these schemes, except that None must be used by itself. |
When deployed as an OpenID Connect Relying Party (RP), PingFederate authenticates through client secret and private key JSON web tokens (JWT). It also handles the scenario where authentication is not required.