You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "David Valeri (JIRA)" <ji...@apache.org> on 2010/02/05 15:26:27 UTC
[jira] Created: (CXF-2656) WS-SP signed elements assertion cannot
be applied to portions of the signature in outbound processing
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
Affects Versions: 2.3
Reporter: David Valeri
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2656) WS-SP signed elements assertion cannot
be applied to portions of the signature in outbound processing
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri updated CXF-2656:
------------------------------
Component/s: WS-* Components
> 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
> Reporter: David Valeri
>
> 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.
-
You can reply to this email to add a comment to the issue online.