fix: JWT Token JSON Parsing Error with non-ASCII characters#100
Open
moon-jun wants to merge 1 commit intodevopskube:masterfrom
Open
fix: JWT Token JSON Parsing Error with non-ASCII characters#100moon-jun wants to merge 1 commit intodevopskube:masterfrom
moon-jun wants to merge 1 commit intodevopskube:masterfrom
Conversation
fix: JWT Token Json Parsing Error At using Korean, Turkish...else purpose 1. JWT use Base 64 URL encoding So, Before Base 64 Decoding URL-safe character(-, _) should change to (+, /) 2. Including korean JWT payload is Json string That encoding by UTF-8 So, ByteArray Decoded by Base64 should change to UTF-8 String 3. Finally payload is Json So, Parsing And return To JS Object
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
1 participant
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.
fix: JWT Token JSON Parsing Error with non-ASCII characters
Purpose:
JWT tokens use Base64 URL encoding. Therefore, before performing Base64 decoding, URL-safe characters ('-', '_') must be replaced with standard Base64 characters ('+', '/').
The JWT payload (which may include non-ASCII characters such as Korean or Turkish) is a JSON string encoded in UTF-8. Thus, the byte array obtained after Base64 decoding should be converted into a UTF-8 string.
Finally, parse the UTF-8 string as JSON and return the resulting JavaScript object.