Having the same issue with a sender vouches saml token. I'm using 3.0.0-SNAPSHOT and I believe I have the correct jars for wss4j. 2.0.0 most say beta. I'm not sure what the issue is because as soon as it tries to invoke the WSS4jInInterception it logs "Finished servicing http request on thread" and no additional logging. This is running in Glassfish v.2.1.1 which could be adding to the problem. I think I worked out the classloader issues. My service was running good without WS security.
2014-02-15 19:57:11.865 [DEBUG] org.apache.cxf.phase.PhaseInterceptorChain:305 - Invoking handleMessage on interceptor org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor@1676032 2014-02-15 19:57:11.866 [DEBUG] org.apache.cxf.transport.servlet.ServletController:228 - Finished servicing http request on thread: Thread[httpSSLWorkerThread-20243-1,10,Grizzly] -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-Service-can-t-process-PublicKey-SAML-Sender-Vouches-IssuedToken-in-WS-Policy-tp5739904p5740029.html Sent from the cxf-user mailing list archive at Nabble.com.
