0 Replies Latest reply on Jun 1, 2010 9:47 AM by blahblah

    Ws-security policy, policy alternatives cannot be satisfied

    blahblah

      Hi I cannot seem to get ws-security policy to work within servicemix 4.2 at all. I've been able to deployed a web service with ws-security policy using CXF/Jaxws deployed on Tomcat but that doesn't translate well into the Osgi/JBI environment in Servicemix 4.2. I've been at this for weeks and its suppose to be cleaner and easier than using WSS4JInInterceptors but I just cannot seem to get past this error. Is there something I'm doing wrong?

       

      Error response:

       

      These policy alternatives can not be satisfied:

              UsernameToken

       

      Edited by: blahblah on Jun 1, 2010 1:46 PM