[
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.
