don't croak on an unknown zip method while unzipping the payload#39
Open
MichaelDaum wants to merge 2 commits intoDCIT:masterfrom
Open
don't croak on an unknown zip method while unzipping the payload#39MichaelDaum wants to merge 2 commits intoDCIT:masterfrom
MichaelDaum wants to merge 2 commits intoDCIT:masterfrom
Conversation
LinkedIn's OpenID puts an "RS256" into the "zip" property of the JWT header. Which might be wrong obviously as the rest of the payload is uncompressed. So better ignore this and return the payload as is.
Contributor
|
The standard https://datatracker.ietf.org/doc/html/rfc7516#section-4.1.3 says: To me it sounds like when the "zip" properties is present but we do not understand its content we should stop/fail/croak. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
LinkedIn's OpenID puts an "RS256" into the "zip" property of the JWT header. Which might be wrong obviously as the rest of the payload is uncompressed. So better ignore this and return the payload as is.