-
-
Notifications
You must be signed in to change notification settings - Fork 467
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
Exception if JWK set kid
in single key and JWS does not specify kid
#462
Labels
Comments
I am seeing this same behavior, as well |
+1 I am also running into this issue |
@dklimpel yeah. A PR is welcome. |
Current error message in version
|
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This issue is related to #222
kid
is optional in JWK, RFC7517kid
is optional in JWS header, RFC7515If JWKS only one key specifies and the JWS header has no
kid
specified the following behaviour occurs:kid
jwt.decode
find and uses the key.kid
jwt.decode
fails and does not find the key and fails.Error Stacks
To Reproduce
A minimal example to reproduce the behavior:
Expected behavior
If no
kid
is specified in the JWS header, the only key in the JWKS should be used, regardless of whether it has akid
or not.Environment:
Additional context
I have created the dummy
id_token
and JWKS with https://oauth.tools/ - "CREATE JWT".The export of the data (to reproduce) is attached here.
If wanted I can try to create a PR.
Create-JWT.zip
The text was updated successfully, but these errors were encountered: