feat: throw custom error when jws protected header is not valid json #244
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR adds additional check in JWS verification allowing for catching malformed JWS protected header. Previously, when user provided token which "appeared" like a well-formed JWS, but in reality protected header could not be
JSON.parse-d,SyntaxErrorwould be thrown. With this PR,JWSInvalid('JWS Protected Header is invalid')is thrown.E.g., having JWT (with
1prepended):Previously, when using
jwtVerify:was thrown. After this PR,
JWSInvaliderror with messageJWS Protected Header is invalidand can be handled by user.