Hi Guy
setting these 2 props works for me.
     <parameter name="enableNamespacePrefixOptimization" value="false" />
     <parameter name="disablePrettyXML" value="true"/>

thanks
Anamitra


                                                                       
             "Dittmann,                                                
             Werner"                                                   
             <werner.dittmann@                                          To
             siemens.com>              "Guy Rixon" <[EMAIL PROTECTED]>,
                                       <[email protected]>       
             03/16/2006 09:10                                           cc
             AM                                                        
                                                                   Subject
                                       AW: Problems with signatures    
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       




AFAIK there is a switch / parameter in the Axis WSDD files
to disable XML pretty printing. Maybe this "feature" is enabled
by default - pretty printing always destroys the signature
hashes.

Also there is a parameter for Axis to disable some sort
of namespace optimization - sorry but I haven't the parameter
names at hand.

Regards,
Werner

> -----Ursprüngliche Nachricht-----
> Von: Guy Rixon [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 16. März 2006 14:01
> An: [email protected]
> Betreff: Problems with signatures
>
> Hi,
>
> can you help me with a signature problem?  I have a client
> and service, both
> using WSS4J 1.0.0. The client signs the SOAP body of the
> request, but the
> signature checking in the service always fails at the XMLSec
> level. The
> signature uses a direct reference to a BinarySecurityToken,
> and the service
> seems to be reading the token properly; at least, it gets the
> subject DN
> right.
>
> I've checked the signature in the client immediately after
> signing and it
> verifies correctly there. Something bad seems to be happening
> to the XML on
> the way to the service, but I can't think what. No other
> special handlers are
> involved.
>
> This is all with Axis 1.3 and "local" transport, BTW.
>
> Thanks,
> Guy
>
> Guy Rixon
[EMAIL PROTECTED]
> Institute of Astronomy                             Tel: +44-1223-337542
> Madingley Road, Cambridge, UK, CB3 0HA                     Fax:
> +44-1223-337523
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to