Use jwt v2.9.2's public claims verification API #465
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a continuation of zquestz#464, which fixed backward compatibility with jwt v2.9.0 and v2.9.1. v2.9.2 brought back the removed APIs, for backward compatibility, but marked them as internal only and/or deprecated. For context, see the discussion here: * jwt/ruby-jwt#623 * jwt/ruby-jwt#626
|
Please note: this passes tests (at least locally, for me) but I haven't actually tested this "for real" yet. Hopefully by the end of the day. |
|
I forgot to update the PR, but I've had this running in production with no errors since early last week. |
|
Ahh thanks, going to look at this soon, just been on vacation this week. =) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a continuation of #464, which fixed backward compatibility with jwt v2.9.0 and v2.9.1. v2.9.2 brought back the removed APIs, for backward compatibility, but marked them as internal only and/or deprecated.
For context, see the discussion here: