Skip to content

fix: also use jwks keys without "use" field#254

Merged
sevensolutions merged 1 commit intosevensolutions:mainfrom
bkw:no-not-require-optional-use-sig-in-keys
Feb 7, 2026
Merged

fix: also use jwks keys without "use" field#254
sevensolutions merged 1 commit intosevensolutions:mainfrom
bkw:no-not-require-optional-use-sig-in-keys

Conversation

@bkw
Copy link
Contributor

@bkw bkw commented Feb 7, 2026

According to RFC 7517, the field "use" is optional. Requiring jkms responses to include it reduces compatibility with implementations which rightfully exclude it.

In the spirit of being conservative in what you send and liberal in what you accept, I also submitted a PR for Rauthy, which is an excellent oidc provider that does not add this field. But I think we really should also accept keys without it, hence this PR.

According to RFC 7517, the field "use" is optional:https://datatracker.ietf.org/doc/html/rfc7517#section-4.2
Requiring jkms responses to include it reduces compatibility with implementations which rightfully exclude it.
@sevensolutions
Copy link
Owner

Thank you @bkw 👍

@sevensolutions sevensolutions changed the title fix: also use jkms keys without "use" field fix: also use jwks keys without "use" field Feb 7, 2026
@sevensolutions sevensolutions merged commit a34daea into sevensolutions:main Feb 7, 2026
2 checks passed
@bkw bkw deleted the no-not-require-optional-use-sig-in-keys branch February 10, 2026 12:59
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.

2 participants