Re: Character problem with axis2 - rampart 1.3

by Nunny :: Rate this Message:

Hi Laszlo,
Rampart 1.3 was zipped with Apache XML Security 1.4.0 and it has a bug [1] when it comes to creating signatures containing non ascii characters. This is fixed in XML Security 1.4.1 and can you try replacing the XML Security 1.4.0 library with XML Security 1.4.1 [2] .

thanks,
nandana

[1] - https://issues.apache.org/bugzilla/show_bug.cgi?id=41462
[2] - http://xml.apache.org/security/dist/java-library/

On Thu, Oct 2, 2008 at 9:34 PM, Laszlo Benke <laszlo.benke@...> wrote:

Hello!

I've made a ws-security client which is communicating to a Websphere
webservice with signed body, using x503Token. It works fine if the body
doesn't contain any non iso-8859-1 characters. But if it contains I've got
org.apache.ws.security.WSSecurityException: The signature verification
failed exception. The server sends the answer in utf-8 and it sets
context-type to text/xml; charset=utf-8. The received message is also good,
when I take a look at this line in the log:
org.apache.rampart.MESSAGE.invoke:78 - ***********************
RampartReceiver received. But later in the log it becomes wrong
here:org.apache.ws.security.message.EnvelopeIdResolver.engineResolve:145 -
exit engineResolve, result: XMLSignatureInput/Element/

Difference in the lines are the following:
<errText>A Casco szerződés nem élő.</errText>
<errText>A Casco szerzĹ'dĂ©s nem Ă©lĹ'.</errText>

Anybody has idea what can I do with this problem.

Thanks for the answers
Laszlo

--
View this message in context: http://www.nabble.com/Character-problem-with-axis2---rampart-1.3-tp19781765p19781765.html
Sent from the Axis - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@...
For additional commands, e-mail: axis-user-help@...

--
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

« Return to Thread: Character problem with axis2 - rampart 1.3