camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Bernhardt (Created) (JIRA)" <>
Subject [jira] [Created] (CAMEL-4688) CXF Security Interceptor does not work in Camel Proxy
Date Wed, 16 Nov 2011 15:34:51 GMT
CXF Security Interceptor does not work in Camel Proxy

                 Key: CAMEL-4688
             Project: Camel
          Issue Type: Bug
          Components: camel-cxf
    Affects Versions: 2.8.2
         Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: C:\Program Files\apache-maven-3.0.3
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_25\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
            Reporter: Jan Bernhardt

In tried to setup a proxy webservice which takes care for authentication.
But even thou I added the right interceptor in my cxf:cxfEndpoint I receive the following
soap fault, when providing my credentials to the proxy service:

         <faultstring>MustUnderstand headers: [{}Security]
are not understood.</faultstring>

I was looking in the debug modus, if the method getUnderstoodHeaders() in AbstractWSS4JInterceptor
was called and discoverd that it was not. Therefore cxf does not know that it could handle
my security-token.

I tried to extend the cxf proxy example, which is shipped with camel. Here is my cxfEndpoint

    <!-- this is the CXF webservice we use as front end -->
    <cxf:cxfEndpoint id="reportIncident"
			<bean id="logInbound" class="org.apache.cxf.interceptor.LoggingInInterceptor"/>
			<bean class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor" />
			<bean id="authenticationInterceptor" class="">
						<entry key="action" value="UsernameToken" />
						<entry key="passwordType" value="PasswordText" />
						<entry key="passwordCallbackClass" value=""

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message