Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a new JWKeyNotFound exception #292

Merged
merged 1 commit into from
May 21, 2022
Merged

Conversation

simo5
Copy link
Member

@simo5 simo5 commented May 20, 2022

This new Exception is returned only for the newly introduced support for
using JWKset.
This patch also includes a bugfix for jwe to be able to successfully
decrypt using a JWKSet, which was non-functional, and a direct test for
both JWE and JWS to insure no regressions in JWKSet support.

Also restores use of JWTMissingKey for backwards compatibility.

Fixes #291

@simo5
Copy link
Member Author

simo5 commented May 20, 2022

@nonathaj this should fix #291 can you confirm it works for you?

This new Exception is returned only for the newly introduced support for
using JWKset.
This patch also includes a bugfix for jwe to be able to successfully
decrypt using a JWKSet, which was non-functional, and a direct test for
both JWE and JWS to insure no regressions in JWKSet support.

Also restores use of JWTMissingKey for backwards compatibility.

Signed-off-by: Simo Sorce <simo@redhat.com>
@bturk-rh
Copy link

@simo5, I work with @nonathaj and can confirm this works for our use case. Thanks for the quick turn around!

@simo5 simo5 merged commit 997b900 into latchset:master May 21, 2022
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.

1.3.0 breaks compatibility and should have been 2.0.0
2 participants