Skip to content

Support for client assertions (private_key_jwt) #5935

@EnzoAlbornoz

Description

@EnzoAlbornoz

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

RFC 7521: Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants introduced a new authentication type, private_key_jwt. This method is used by providers like Okta and is recommended for financial-grade APIs due to the increased security it provides with asymmetric keys.

Describe the solution you'd like

Include a new token authorization type called private_key_jwt (or pk as a shorthand) for validating authorization codes.

Describe alternatives you've considered

  • Using client secret: Financial-grade APIs are recommended to use private_key_jwt due to asymmetric key security features, so switching to it shouldn't be encouraged.
  • Rolling my own auth: Well, this is hard, isn't it 🥲?

Additional context

No response

Metadata

Metadata

Labels

identityOAuth/OIDC provider, MCP, device flowoauthSocial providers, OAuth flows, generic-oauth

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions