You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2013/01/17 11:56:13 UTC

[jira] [Commented] (CXF-4759) No security headers created for policy with no Binding assertion

    [ https://issues.apache.org/jira/browse/CXF-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556056#comment-13556056 ] 

Colm O hEigeartaigh commented on CXF-4759:
------------------------------------------


Have you actually tried that policy to see if it works? A special StaX based interceptor (UsernameTokenInterceptor) handles the case of UsernameToken policies that are not attached to a binding. See this test for example:

http://svn.apache.org/viewvc/cxf/trunk/systests/ws-security-examples/src/test/java/org/apache/cxf/systest/wssec/examples/ut/UsernameTokenTest.java?view=markup
http://svn.apache.org/viewvc/cxf/trunk/systests/ws-security-examples/src/test/resources/org/apache/cxf/systest/wssec/examples/ut/DoubleItUt.wsdl?view=markup

Colm.
                
> No security headers created for policy with no Binding assertion
> ----------------------------------------------------------------
>
>                 Key: CXF-4759
>                 URL: https://issues.apache.org/jira/browse/CXF-4759
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.7.0
>            Reporter: Paton Wong
>         Attachments: UsernameToken-Plain.xml
>
>
> For instance if a SOAP service has a policy with a supporting token of UsernameToken without a TransportBinding, SymmetricBinding or AsymmetricBinding then CXF will not send any security header.
> In PolicyBasedWSS4JOutInterceptorInternal.handleMessage, there is an attempt to create a dummy TransportBinding, when the policy itself had not specified a binding. However, without a TransportToken, the TransportBindingHandler will ignore any supporting tokens.

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