-
Notifications
You must be signed in to change notification settings - Fork 236
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
Allow JWT to not contain a "kid" value #55
Allow JWT to not contain a "kid" value #55
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️ |
bump |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. Do you mind adding a test in jwksClient.tests.js
to test for the scenario when JWKS endpoint returns a single key and no KID is provided
Thank you 🙏
…turns a single key
…n passports.tests.js
3768134
to
31c7f65
Compare
I've fixed that test up (+1 more with the same issue), rebased on top of master, and added a similar test to passport.test.js |
Thank you for the quick follow up @dejan9393 |
Allow JWT to not contain a "kid" value when the JWKS endpoint only returns a single key.
The spec marks this claim as optional.