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.

Sign up for GitHub

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

Jump to bottom

Support jwt versions < 3 #94

Closed
mvastola opened this issue Oct 11, 2017 · 1 comment
Closed

Support jwt versions < 3 #94

mvastola opened this issue Oct 11, 2017 · 1 comment
Assignees
@mvastola
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@mvastola
Copy link
Contributor

The jwt gem is now on version 2.1.0 and has one feature that applies particularly to users using this gem for oauth authentication against Google:

When calling JWT.decode, in version 2+, the custom_options hash now accepts an array to validate against multiple possible iss candidates. (The Google oauth specifications state that the iss may be set to either https://accounts.google.com or accounts.google.com.)
@mvastola
Copy link
Contributor Author

I'm dumb and should really learn to search better before I post issues.
Fixed in c9d21b3; dup of #93.

@yoshi-automation yoshi-automation added 🚨 This issue needs some love. triage me I really want to be triaged. labels Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mvastola mvastola

Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mvastola @yoshi-automation