Bugfix: Enable non-ascii characters in JWT#79
Open
tom-010 wants to merge 1 commit intoappsup-dart:masterfrom
Open
Bugfix: Enable non-ascii characters in JWT#79tom-010 wants to merge 1 commit intoappsup-dart:masterfrom
tom-010 wants to merge 1 commit intoappsup-dart:masterfrom
Conversation
Problem: When processing the response from an OpenID-Provider, the string is not decoded using UTF-8. Therefore, no non-ascii characters like german "Umlaute" (like ä, ü, ö) are possible in the JWT and therefore in the name in the JWT (like Jürgen). Fix: in `lib/src/http_util.dart` `_processResponse`: before calling `json.decode` of the response, first decode it via `utf8.decode`. Result: Umlaute and other non-ascii characters are now possible in the JWT and its fields like the name.
|
@rbellens Can this be merged please? Thanks! |
|
+1 |
Contributor
|
As @bvoq mentions, |
|
pls merge this pr we have this problem in arabic characters |
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
5 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.
Problem: When processing the response from an OpenID-Provider, the string is not decoded using UTF-8. Therefore, no non-ascii characters like german "Umlaute" (like ä, ü, ö) are possible in the JWT and therefore in the name in the JWT (like Jürgen).
Fix: in
lib/src/http_util.dart_processResponse: before callingjson.decodeof the response, first decode it viautf8.decode.Result: Umlaute and other non-ascii characters are now possible in the JWT and its fields like the name.