Hello,

I have been playing with SMX4 for few days now and I started liking it
already, as it nicely integrates the best 3 things: spring, osgi & JBI (in
addition to Camel/AMQ/CXF and others). 

Thanks to you guys for a great job!

The question I had is related to enabling ws-security to a service on CXF.
To understand this, I thought it is good to take the shipped cxf-wsdl-first
example and try to make it ws-security enabled by:

adding WSS4J interceptor on cxf-bc su:

<code>
<beans xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0";
       xmlns:person="http://servicemix.apache.org/samples/wsdl-first";>

  <cxfbc:consumer wsdl="classpath:person.wsdl"
                      targetService="person:PersonService"
                      targetInterface="person:Person">
        <!--    WS-Security interceptors --> 
                        <cxfbc:inInterceptors>
                                <ref bean="wss4jin"/>
                        </cxfbc:inInterceptors>  
  </cxfbc:consumer>
        
        <bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor"
                                id="wss4jin">
                <constructor-arg>
                        <map>
                        <entry key="action" value="UsernameToken"/>      
                        <entry key="passwordType" value="PasswordDigest" /> 
                        <entry key="passwordCallbackClass"
                                
value="org.apache.servicemix.samples.wsdl_first.ServerPasswordCallback"/>
                        </map>
                </constructor-arg>
        </bean>
        
</beans>
</code> 


and then testing it on soap-ui client with:

<code>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types";>
   <soapenv:Header><wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";><wsse:UsernameToken
wsu:Id="UsernameToken-2956574"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";><wsse:Username>smx</wsse:Username><wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest";>7vBUrC3FJYywtWp2S9t6RKgT0GQ=</wsse:Password><wsse:Nonce>XCTIgEZbX0l9qJQl2nXEkg==</wsse:Nonce><wsu:Created>2009-04-14T11:03:09.342Z</wsu:Created></wsse:UsernameToken></wsse:Security></soapenv:Header>
   <soapenv:Body>
      <typ:GetPerson>
         <typ:personId>1</typ:personId>
      </typ:GetPerson>
   </soapenv:Body>
</soapenv:Envelope>
</code> 
 
but the response is:

<code>
       <faultcode>soap:Client</faultcode>
         <faultstring>Problems creating SAAJ object model</faultstring>
</code>

Any idea what i am missing...?

Thanks!

-- 
View this message in context: 
http://www.nabble.com/SMX4-and-WS-Security-tp23037639p23037639.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to