Sure, it works also with WS-Security Policy. Actually, it is recommended way to enable security in CXF. Technically CXF just activates appropriate interceptors based on WS-Security Policy assertions using PolicyInterceptorProvider.
Important that your interceptor is called before WSS4J interceptors, otherwise crypto provider settings would not be accepted. Cheers, Andrei. > -----Original Message----- > From: martin [mailto:[email protected]] > Sent: Dienstag, 20. November 2012 12:41 > To: [email protected] > Subject: RE: Expanding a webservice client to handle changing keys. > > --Andrei Shakirin > > Will that not defeat the purpose of using the WS-Security Policy engine? I > will > be using clients created in several languages so loosing the WS-Security > segments would be bad. > Can i still keep the WS-Security Policy thorough this approach? > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/Expanding- > a-webservice-client-to-handle-changing-keys-tp5718802p5718822.html > Sent from the cxf-user mailing list archive at Nabble.com.
