[
https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642718#comment-13642718
]
Colm O hEigeartaigh commented on WSS-436:
-----------------------------------------
Hi Marc,
Yes it does work in the DOM code. See the following comment in WSHandler:
// See if the Signature and Timestamp actions (in that order) are
defined, and if
// the Timestamp is to be signed. In this case we need to swap the
actions, as the
// Timestamp must appear in the security header first for signature
creation to work.
But the question here is whether it is possible to put a security header
element that is being signed above the signature at all?
Colm.
> Outbound StaX code should fail on not finding a signature/encryption part
> -------------------------------------------------------------------------
>
> Key: WSS-436
> URL: https://issues.apache.org/jira/browse/WSS-436
> Project: WSS4J
> Issue Type: Bug
> Reporter: Colm O hEigeartaigh
> Assignee: Marc Giger
> Fix For: 2.0
>
>
> The outbound StaX code should fail on not finding a signature/encryption
> part. Perhaps we could just add a boolean to SecurePart indicating whether it
> was satisfied or not, and then loop through the SecurePart lists when we're
> done to check everything was matching.
> With the current code a user might specify the wrong namespace and then
> assume security was applied.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
