private_key_jwt configuration for ClientCredentials (RFC 7523 /
SEP-1046): the client proves its identity with a signed JWT client_assertion
instead of a shared secret. The assertion is signed by the SDK’s own
private_key_jwt machinery — no secret is ever sent to the token endpoint.
Extends
ClientCredentialsBaseOptions
Properties
algorithm
ES256 or RS256.
audience
aud claim. Required — there is no safe default, because
this provider does no discovery and cannot learn the authorization server’s
identity on its own. RFC 7523 §3 recommends the authorization server’s
issuer identifier; some servers instead verify against the token endpoint
URL. Set whichever your server checks (issuer is the more common choice).
authMethod?
claims?
iss/sub/aud/exp/iat/jti.
clientId
Inherited from
clientSecret?
jwtLifetimeSeconds?
privateKey
refreshBufferSeconds?
Inherited from
scope?
Inherited from
store?
tokenEndpoint alone, with no client identity in it — use one store per
credential identity. Do not share a persistent store across two
ClientCredentials instances that have different clientId/clientSecret/
privateKey but the same tokenEndpoint; they will read and overwrite
each other’s cached tokens.