This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
Changing the Decoding type to Raw URL encoding. #51
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.
Changing the Decoding type to Raw URL encoding.
JWTs make use of the base64url encoding as defined in RFC 4648 [RFC4648]. As allowed by Section 3.2 of the RFC, this specification mandates that base64url encoding when used with JWTs MUST NOT use padding. The reason for this restriction is that the padding character ('=') is not URL safe. [https://www.ietf.org/archive/id/draft-jones-json-web-token-02.html#rfc.section.7)].
The base64 Std / URL parsers expect a padding character (=), which is optional and the absence of which can lead to unexpected failures. (https://pkg.go.dev/encoding/base64). There is a github issue which talks about the same - Base64 decoding not working correctly golang/go#46257
Also added extra logging for debugging.