Verifier (OneOf)#

Path: /profiles/profile/settings/authorization-server/client-store/config-backed/client/secondary-authentication-method

Describes how the client is authenticated

Parameters#

NameTypeRequiredDefaultDescription
secretstringoptional-A password used by the client
asymmetric-keyleafref → /base:facilities/base:crypto/base:signature-verification-keys/base:signature-verification-key/base:idoptional-A public key that corresponds to the private key the client will use to sign a token with to authenticate itself
jwksstring (length: 1..9223372036854775807)optional-A JWKS providing keys that can be used to verify JWT assertions. The JSON String should be base64-encoded.
symmetric-keystring (length: 1..9223372036854775807)optional-A secret key that the client will use to sign or integrity protect a token with to authenticate itself
no-authenticationbooleanoptionalfalseWhen no-authentication is selected, the client is a public client. Can only be used for clients that requests tokens, and only makes sense if they use the token endpoint (i.e. use the code flow).
credential-managerleafref → /base:processing/base:credential-managers/base:credential-manager/base:idoptional-The Credential Manager to use to transform the client secret. For configured clients, this credential manager is also used to retrieve the client secret from the configured data source on the credential manager

Subsections#

NameTypeDescription
jwks-uri SectionA key present in a JWKS referenced by an URI, accessed via an optional HTTP client ID
mutual-tls-by-proxy Section
mutual-tls Section

Was this helpful?