[
https://issues.apache.org/jira/browse/CXF-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006982#comment-13006982
]
David Valeri commented on CXF-2656:
-----------------------------------
It is likely that it is still an issue. It is however, low priority. I will
try to put together a test case for it this week.
> WS-SP signed elements assertion cannot be applied to portions of the
> signature in outbound processing
> -----------------------------------------------------------------------------------------------------
>
> Key: CXF-2656
> URL: https://issues.apache.org/jira/browse/CXF-2656
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.3.0
> Reporter: David Valeri
> Fix For: NeedMoreInfo
>
>
> AsymetricBinding can't sign parts created by the WSS4J signature processing
> code. Because AsymetricBinding calculates signature covered parts before
> creating/embedding the constructs of the WS-S signature into the SAAJ DOM, it
> cannot find things like the ws:KeyInfo to sign.
> Changing the order of operations is necessary to resolve this issue. It
> would appear that WSS4J supports this capability any time after prepare has
> been called as it can accomplish this feat when using the build convenience
> method.
> Test case is pending.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
