Hi,
I've run into the same problem with wss4j 1.5.6 and axis 1.4.
So, can I sign a soap message despite this bug? Are there ways to
circumvent it or to fix it?
And why doesn't it bother us when using the WSDoAllHandlers (I need to
use the wss4j API, since I'm trying to protect specific WS operations
only) ?
Thank you
Bauer Horscht
Colm O hEigeartaigh schrieb:
For the record, in case anyone else runs into this problem...I
addressed this issue on security-dev. The problem is a bug in the
Axis1 SAAJ implementation:
http://markmail.org/message/qkjrws3zzyczwim5
Colm.
------------------------------------------------------------------------
*From:* Colm O hEigeartaigh [mailto:[email protected]]
*Sent:* 23 March 2009 11:02
*To:* Mihir Mathuria
*Cc:* [email protected]
*Subject:* RE: Cannot create a
http://www.w3.org/2000/09/xmldsig#:ds:SignatureMethod from a
http://www.w3.org/2000/09/xmldsig#:SignatureMethod element
Can you try it with WSS4J 1.5.6? Also, can you attach the stacktrace
(from WSS4J 1.5.6) as well as your configuration.
Colm.
------------------------------------------------------------------------
*From:* Mihir Mathuria [mailto:[email protected]]
*Sent:* 20 March 2009 18:33
*To:* Colm O hEigeartaigh
*Cc:* [email protected]
*Subject:* Re: Cannot create a
http://www.w3.org/2000/09/xmldsig#:ds:SignatureMethod from a
http://www.w3.org/2000/09/xmldsig#:SignatureMethod element
Hi Colm,
Thanks for the reply.
The Canonicalization algorithm being used is
"http://www.w3.org/2001/10/xml-exc-c14n#
<http://www.w3.org/2001/10/xml-exc-c14n>".
This is the default one. I never specified anything manually.
Anything I should try?
--Mihir.
