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/07/30 19:26:16 UTC
[jira] Created: (CXF-2921) PolicyBasedWSS4JInInterceptor not
asserting TransportBinding assertion when no message layer security is
added
PolicyBasedWSS4JInInterceptor not asserting TransportBinding assertion when no message layer security is added
--------------------------------------------------------------------------------------------------------------
Key: CXF-2921
URL: https://issues.apache.org/jira/browse/CXF-2921
Project: CXF
Issue Type: Bug
Components: WS-* Components
Affects Versions: 2.3, 2.2.10
Reporter: David Valeri
Fix For: 2.3, 2.2.10
When a TransportBinding assertion is used and no message layer security is employed, the WSS4JInInterceptor does not delegate result processing to PolicyBasedWSS4JInInterceptor. As a result, the transport bindings are not asserted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2921) PolicyBasedWSS4JInInterceptor not
asserting TransportBinding assertion when no message layer security is
added
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri reassigned CXF-2921:
---------------------------------
Assignee: David Valeri
> PolicyBasedWSS4JInInterceptor not asserting TransportBinding assertion when no message layer security is added
> --------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2921
> URL: https://issues.apache.org/jira/browse/CXF-2921
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.3, 2.2.10
> Reporter: David Valeri
> Assignee: David Valeri
> Fix For: 2.3, 2.2.10
>
>
> When a TransportBinding assertion is used and no message layer security is employed, the WSS4JInInterceptor does not delegate result processing to PolicyBasedWSS4JInInterceptor. As a result, the transport bindings are not asserted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2921) PolicyBasedWSS4JInInterceptor not
asserting TransportBinding assertion when no message layer security is
added
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894102#action_12894102 ]
David Valeri commented on CXF-2921:
-----------------------------------
I forgot to include the policy sample in the description. By "no message layer security is employed" I meant that no WS-S Security header or child elements are in the SOAP Header. When this element is missing, the WSS4JInInterceptor would return before delegating to PolicyBasedWSS4JInInterceptor. If PolicyBasedWSS4JInInterceptor is not given a chance to #doResults, even if there are no results from WSS4J, it does not assert the TransportBinding assertions. Since this interceptor is solely responsible for asserting that binding, it has to be given a chance to do so, even if no WS-S Security header is in play.
The test case and code changes should demonstrate what I was after, even if the above description is still confusing.
> PolicyBasedWSS4JInInterceptor not asserting TransportBinding assertion when no message layer security is added
> --------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2921
> URL: https://issues.apache.org/jira/browse/CXF-2921
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.3, 2.2.10
> Reporter: David Valeri
> Assignee: David Valeri
> Fix For: 2.3, 2.2.10
>
>
> When a TransportBinding assertion is used and no message layer security is employed, the WSS4JInInterceptor does not delegate result processing to PolicyBasedWSS4JInInterceptor. As a result, the transport bindings are not asserted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2921) PolicyBasedWSS4JInInterceptor not
asserting TransportBinding assertion when no message layer security is
added
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri resolved CXF-2921.
-------------------------------
Resolution: Fixed
> PolicyBasedWSS4JInInterceptor not asserting TransportBinding assertion when no message layer security is added
> --------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2921
> URL: https://issues.apache.org/jira/browse/CXF-2921
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.3, 2.2.10
> Reporter: David Valeri
> Assignee: David Valeri
> Fix For: 2.3, 2.2.10
>
>
> When a TransportBinding assertion is used and no message layer security is employed, the WSS4JInInterceptor does not delegate result processing to PolicyBasedWSS4JInInterceptor. As a result, the transport bindings are not asserted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2921) PolicyBasedWSS4JInInterceptor not
asserting TransportBinding assertion when no message layer security is
added
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894090#action_12894090 ]
Glen Mazza commented on CXF-2921:
---------------------------------
I'm not sure this is a bug. Policy reading requires having the policy and security modules in the classpath (http://cxf.apache.org/docs/ws-securitypolicy.html#WS-SecurityPolicy-EnablingWSSecurityPolicy), which they are by default. Perhaps you're saying just including the former should be enough to activate non-security elements of the policy?
> PolicyBasedWSS4JInInterceptor not asserting TransportBinding assertion when no message layer security is added
> --------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2921
> URL: https://issues.apache.org/jira/browse/CXF-2921
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.3, 2.2.10
> Reporter: David Valeri
> Assignee: David Valeri
> Fix For: 2.3, 2.2.10
>
>
> When a TransportBinding assertion is used and no message layer security is employed, the WSS4JInInterceptor does not delegate result processing to PolicyBasedWSS4JInInterceptor. As a result, the transport bindings are not asserted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.