[
https://issues.apache.org/jira/browse/SYNCOPE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494932#comment-13494932
]
Denis Signoretto commented on SYNCOPE-233:
------------------------------------------
Hi Francesco,
I would expect something like that (UTF-8 instead of false):
...
<entry>
<key>
<value>http.auth.credential-charset</value>
</key>
<value type="java.lang.String">"UTF-8"</value>
</entry>
...
or automatic authentication solve by itself?
<entry>
<key>
<value>http.protocol.handle-authentication</value>
</key>
<value type="java.lang.Boolean">false</value>
</entry>
Bye,
Denis
> Authentication failure using password with special characters
> -------------------------------------------------------------
>
> Key: SYNCOPE-233
> URL: https://issues.apache.org/jira/browse/SYNCOPE-233
> Project: Syncope
> Issue Type: Bug
> Components: console, core
> Affects Versions: 1.0.2-incubating, 1.0.3-incubating
> Environment: Linux x86_64, Oracle 10g (default charset AL32UTF8),
> Apache Tomcat 7.0.26
> Reporter: Denis Signoretto
> Assignee: Francesco Chicchiriccò
> Fix For: 1.0.4-incubating, 1.1.0
>
> Attachments: patch.diff
>
>
> 1) Login as admin: OK
> 2) Create a user with any username and passowrd e.g. test/test: OK
> 3) Logout as admin and login as test/test: OK
> 4) Login as admin: OK
> 5) Change password to test user and use any special char e.g. "èàì": OK
> 6) Logout as admin and login as test: Fail
> Oracle Database is configured to use AL32UTF8 charset as default
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
