Remy, I just thought of a possible solution. Instead of supplying two actions to the same interceptor, maybe one could create two separate interceptors - one handling the USERNAME_TOKEN, the other handling the SIGNATURE actions. (or in my case, timestamp).
Did you ever try this? --Mark remy2009 wrote: > > Sorry, nothing yet. Work with custom SOAP_HEADER with SAML_TOKEN at the > moment. This works for me at the moment but I will probably need > USERNAME_TOKEN with SECURITY in the near. Still waiting for solution. > > Did you happen to try new cxf-2.2.2 version yet? > > Remy > > -- View this message in context: http://www.nabble.com/USERNAME_TOKEN-%2B-SIGNATURE-gives-%22General-security-error-%28WSSecurityEngine%3A-No-password-callback-supplied%29%22-tp21814109p23968654.html Sent from the cxf-user mailing list archive at Nabble.com.
