Skip to content

Issue/586 OIDC client jwks without key algorithm - #592

Open
hhund wants to merge 2 commits into
developfrom
issue/586_OIDC_Client_JWKS_Without_Key_Algorithm
Open

hhund wants to merge 2 commits into
developfrom
issue/586_OIDC_Client_JWKS_Without_Key_Algorithm

Conversation

@hhund

@hhund hhund commented Oct 14, 2026

Copy link
Copy Markdown
Member

Improved OpenId token verification:

  • Consolidated duplicated token validation code in new BaseJwtVerifier.
  • Added test for BaseJwtVerifier.
  • JWKS parsing code now supports key_ops property. The key_ops property is not available to API v2 plugins.
  • Added new properties to configure validation leeway for authentication via bearer tokens and back-channel logout tokens.
  • JWKS keys are now excepted for token validation if they declare use property with value sig, declare a key_ops property array that includes a verify value or no use and key_ops properties.
  • The alg property in JWKS is now optional. Tokens are validated if the JWKS key specifies an algorithm and the token declared the same algorithm. Or if the JWKS key does not specify the algorithm but the token declares RS256, RS384 or RS512 and the key is an RSA key or the token declares ES256, ES384 or ES512 and the key is an EC key. Otherwise the token is rejected without trying a signature validation.

fixes #586

- Consolidated duplicated token validation code in new BaseJwtVerifier.
- Added test for BaseJwtVerifier.
- JWKS parsing code now supports key_ops property.
- Added new properties to configure validation leeway for authentication
via bearer tokens and back-channel logout tokens.
- JWKS keys are now excepted for token validation if they declare use
property with value "sig", declare a key_ops property array that include
"verify" value or no use and key_ops properties.
- The alg property in JWKS is now optional. Tokens are validated if the
JWKS key specifies an algorithm and the token declared the same
algorithm. Or if the JWKS key does not specify the algorithm but the
token declares RS256, RS384 or RS512 and the key is an RSA key or the
token declares ES256, ES384 or ES512 and the key is an EC key. Otherwise
the token is rejected without trying a signature validation.

fixes #586
@hhund hhund added this to the 2.2.0 milestone Oct 14, 2026
@hhund
hhund requested a review from schwzr October 14, 2026 21:56
@hhund hhund self-assigned this Oct 14, 2026
issue/586_OIDC_Client_JWKS_Without_Key_Algorithm
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OIDC Client Fails to Verify Token if JWKS Does Not Define Key Algorithm

1 participant