Hi,
Sign in with a username containing non ASCII chars always fails with CAS
4.0.1 whereas it was working well with our previous CAS install (3.5.0).
For instance if I submit a form with a login like : ééé it does not
work, and in the cas.log I see a failed attempt :
SearchModeSearchDatabaseAuthenticationHandler failed authenticating ééÃ
And then ééà is displayed as username on my form.
That looks like utf-8 displayed with ISO-8859-1.
I 'm using tomcat6 with an apache httpd proxy
I have AddDefaultCharset UTF-8 in my httpd.conf
My tomcat connector is defined like this :
<Connector port="8080" protocol="HTTP/1.1"
address="localhost"
proxyPort="443"
secure="true"
scheme="https"
SSLEnabled="false"
redirectPort="8443"
URIEncoding="UTF-8" />
My JVM options :
JAVA_OPTS="-Duser.country=FR -Duser.language=fr -Xms4096M -Xmx4096M
-Dfile.encoding=UTF8"
I tried adding accept-charset="UTF-8" on the cas login form.
The credential backend is an utf-8 mysql db and tickets are stored in
ehcache.
It used to work with cas 3.5.0 and tomcat6.
Does anybody have a an idea of what could possibly break my chars
encoding between the login form and CAS ?
Thank you for any idea,
--
Raphaël
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
