[jboss-jira] [JBoss JIRA] (WFLY-6823) Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.
[
https://issues.jboss.org/browse/WFLY-6823?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-6823:
--------------------------------------
In EAP7 it was possible to specify both the default charset, and a per browser charset
(based on regex matches of the user agent string). The default charset was UTF-8.
Doesn't work using non-ASCII chars for username and/or password
for BASIC authentication.
-----------------------------------------------------------------------------------------
Key: WFLY-6823
URL: https://issues.jboss.org/browse/WFLY-6823
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Fix For: 11.0.0.Alpha1
Doesn't work using non-ASCII chars for username and/or password for BASIC
authentication.
We noticed it when we looked on JIra issue https://issues.jboss.org/browse/JBEAP-3603.
We JBoss EAP 7 expects encoded UTF-8 strings in code. But we didn't find any
information about it in specification.
It works with Chrome and Opera, but it doesn't work with Firefox.
Since there is no documentation for this username/password limitation it can affect
customers who want to use non-ASCII credentials.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)