[
https://issues.apache.org/jira/browse/WSS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111171#comment-14111171
]
Marc Giger commented on WSS-508:
--------------------------------
Hi Gene,
First of all, I've fixed the issue in santuario trunk. As soon as
xmlsec-2.0.2-SNAPSHOT is built (or build it yourself) you may give it a try.
Secondly, thanks for listing the concrete implementations, as assumed it was
related to the DOM implementation.
To your note regarding what exactly is digested, that's simply the way how XML
Signature works / is designed.
That the body is still verified after the digest missmatch on SignedInfo was
the first thing I noticed when looking at your
issue, but after looking at the code I saw that it is only done when the log
level is set to DEBUG. Otherwise it could
be a potential security issue if it would always/unconditionally be validated.
Marc
> When using "add inclusive prefixes" and EXC C14N - signature cannot be
> validated
> --------------------------------------------------------------------------------
>
> Key: WSS-508
> URL: https://issues.apache.org/jira/browse/WSS-508
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 2.0.0, 2.0.1
> Environment: WAS 7.x, IBM JDK 1.6, WebSphere JAX-WS stack, MS Windows.
> Reporter: Gene B.
> Assignee: Colm O hEigeartaigh
> Attachments: log 01 - signature verification failed with
> InclusiveNamespaces PrefixList.txt, log 02 - signature verification ok -
> signed by SOAP UI.txt, log_03a - consumer - sign message use
> InclusiveNamespaces prefix list.txt, log_03b - provider - signature
> verification failed.txt, request1-printedby-provider-signedby-soapui.xml,
> request1-printedby-provider-signedby-wss4j.xml
>
>
> Security implemented using WSS4J securement/validation action approach. We
> are trying to sign the body.
> The provider is a JAX-WS service running on WebSphere JAX-WS stack. Custom
> handler uses WSS4j to validate security.
> The consumer is a WebSphere JAX-WS dispatch client – also attaching custom
> security handler.
> Signature can be validated on the provider side when EXC C14N
> canonicalization is specified with BST compliance flag relaxed. That is
> because when we chose to add “InclusiveNamespaces” “PrefixList” on the
> consumer side, verification fails. When the same test is done with the SOAP
> UI – signature verifies Ok – so I am blaming the consumer – the signing
> process - not verification process.
> I am attaching a log file which shows verification failure when the
> InclusiveNamespaces option is used. If not for this option – this
> verification would’ve been a success.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
