That fixed the problem!! Thanks a lot!

On Wed, Feb 13, 2008 at 5:19 PM, Hans Guldager Knudsen <[EMAIL PROTECTED]>
wrote:

> Hi!
>
> You could be hit by a bug in xmlsec-1.4 :
>
> http://santuario.apache.org/
>
> /hans
>
>
> Raghuram Sreenath wrote:
> > hello,
> >
> > I use axis 1.4 on both the server side and the client side. My client
> > settings are as follows:
> > <deployment xmlns="http://xml.apache.org/axis/wsdd/";
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> >  <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> >   <globalConfiguration >
> >    <requestFlow >
> >     <handler name="Addressing" type="java:a.b.AddressHandler"/>
> >     <handler name="DoSecuritySender"
> > type="java:org.apache.ws.axis.security.WSDoAllSender" >
> >      <parameter name="action" value="Timestamp Signature"/>
> >      <parameter name="signatureParts"
> > value="{Element}{
> http://schemas.xmlsoap.org/soap/envelope/}Body;{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp<http://schemas.xmlsoap.org/soap/envelope/%7DBody;%7BElement%7D%7Bhttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd%7DTimestamp>
> > <
> http://schemas.xmlsoap.org/soap/envelope/%7DBody;%7BElement%7D%7Bhttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd%7DTimestamp
> >"/>
> >      <parameter name="signatureKeyIdentifier" value="DirectReference"/>
> >      <parameter name="user" value="security-client"/>
> >      <parameter name="signaturePropFile" value="crypto.properties"/>
> >      <parameter name="passwordCallbackClass"
> > value="a.b.PWCallbackHandler"/>
> >     </handler>
> >    </requestFlow >
> >   </globalConfiguration >
> > </deployment>
> >
> > So, I intend to sign the body and Timestamp elements of my message and
> > send it to the server.
> > The setup works fine if the body contains only ascii characters. But
> > if it contains strange UTF-8 characters ( like umlaut - ŭ ) The server
> > side errors out with a "Signature verification Failed" exception.
> >
> > Since the error occurs only when there are special characters and
> > works fine otherwise, I am not doubting other parts of my setup (like
> > my crypto.properties setting or having strange characters inserted
> > after calculating the signature etc.)
> > Any ideas why this happens?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to