Hi,
On our side we have the same configuration, but I can't tell you about
the samlservice exactly...
But things which are sure are :
you need to have you local to UTF-8 set on the server where you JBOSS is
running, a var that you could use also is to launch your jboss with
-Dfile.encoding=UTF-8 (working for TOMCAT so normaly for JBOSS).
After that, normaly, on your php you should receve correctly the
$xml_response after you applied utf8_encode and utf8_decode on attributes...
Else you can watch at least with the serviceValidate if your attributes
returned are UTF-8 encoded, watch also in your browser settings to check
if the encoding type if well recognized...
Hope this will help.
- Julien
Danny B. a écrit :
Hi,
I am having problems with receiving special chars like
<AttributeValue>é.ö.û.à</AttributeValue>
Without the utf-8 filter it got in my apache log I recieved this.
\xe9.\xf6.\xfb.\xe0 (latin)
The php client froze on this code.
It appears we sent the message in ISO-8859-1 instead of UTF-8. Because when
we used utf8_encode($xml_response) in the php example, we could read the
response.
When I looked in my cas-java-demo, I received: ?.?.?.?
So we decided to change it, to use UTF-8 character encoding
Now when I look in my apache log. i see
<AttributeValue>\xc3\xa9.\xc3\xb6.\xc3\xbb.\xc3\xa0</AttributeValue>
When I looked in my cas-java-demo, I received: ??.??.??.??
This is with the spring utf-8 filter.
I am using:
cas-server version 3.3.1
cas-client version 3.1.4
Server: JBoss 4.2.2. running on Ubuntu.
LDAP: utf-8
Steps i have undertaken:
JBoss connector config:
connector: added URIEncoding="UTF-8"
Spring config
Filter UTF-8
Saml10SuccessResponseView
added response.setCharacterEncoding("UTF-8");
All help is very much appreciated.
Thanks in advance.
--
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
