[
https://issues.apache.org/jira/browse/SYNCOPE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493883#comment-13493883
]
Denis Signoretto commented on SYNCOPE-233:
------------------------------------------
Hi,
the issue seams realted to syncope-console and the Spring Rest authenticationt
calls.
The rest call uses Basic Authentication. The issue seams to be generated
because basic
auth do not define a specific charset for password encoding.
http://stackoverflow.com/questions/7242316/what-encoding-should-i-use-for-http-basic-authentication
Apache HttpClient follow RFC and by default do not define a speficic encoding
charset.
http://hc.apache.org/httpclient-3.x/preference-api.html
I solved the problem (I'm not sure it's the best elegant solution) forcing
UTF-8 credentials encoding in the Login.java autenticate() method.
See attached patch file.
Probably it's not the best and elegant solution :)
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
> Environment: Linux x86_64, Oracle 10g (default charset AL32UTF8),
> Apache Tomcat 7.0.26
> Reporter: Denis Signoretto
>
> 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
