You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.decode
of 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.
Pull Request: I already created a pull-request for it: Bugfix: Enable non-ascii characters in JWT
The text was updated successfully, but these errors were encountered: