[
https://issues.apache.org/jira/browse/WSS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498266
]
[EMAIL PROTECTED] commented on WSS-39:
-------------------------------------
ATTENTION!
A message you recently sent to a 0Spam.com user with the subject "[jira]
Commented: (WSS-39) Digital signature of SO..." was not delivered because they
are using the 0Spam.com anti-spam service. Please click the link below to
confirm that this is not spam. When you confirm, this message and all future
messages you send will automatically be accepted.
http://www.0spam.com/v.cgi?user=1086966126&verify=724829
========================================
This is an automated message from 0Spam.com.
Please do not reply to this Email.
Looking for a free anti-spam service?
Visit us at http://www.0spam.com to find out more.
> Digital signature of SOAP bodies fails when using Axis 1.3
> ----------------------------------------------------------
>
> Key: WSS-39
> URL: https://issues.apache.org/jira/browse/WSS-39
> Project: WSS4J
> Issue Type: Bug
> Environment: WSS4J 1.0.0, Axis 1.3, Sun JDK1.4.2
> Reporter: Guy Rixon
> Assigned To: Davanum Srinivas
> Priority: Critical
>
> Digital signature of SOAP bodies fails when using Axis 1.3 but works when
> using Axis 1.2.1: the message is signed without reported errors but the
> signature verification fails.
> Inspection of the logs from the various libraries, notably XMLSec, shows that
> the digest of the reference to the SOAP body is verified but the actual
> signature on the SignedInfo fails verification.
> Experiments with the client-side code show that the envelope, in the form of
> an org.w3c.dom.Document, has a correct, verifiable signature on return from
> WSSignEnvelope.build, but an incorrect signature after it has been serialized
> into the MessageContext and recovered as a Document within the same Handler.
> I.e., this problem is not due to the client's pivot handler or to handlers in
> the service.
> The bytes of the signature encoded in the message seem not to be changed
> between successful and unsucecssful verifications. Therefore, presumably,
> something in Axis is disturbing the XML in the SignedInfo such that the
> canonicalization fails. In my test code and handler I set the properties
> enableNamespacePrefixOptimization to false and disablePrettyXML to true, but
> it makes no difference.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
