Hi,

I thought you already cache it on cxfbc consumer side, :-)
Anyway, yeah, you need a customer interceptor on cxf consumer to cache it, the key code should be like

            SecurityToken token = message.get(SecurityToken.class);
if (token != null && token.getTokenType() == TokenType.UsernameToken) {
                UsernameToken ut = (UsernameToken)token;
                name = ut.getName();
                password = ut.getPassword();
            }
You need ensure your customer Interceptor is after WSS4JInInterceptor and before JAASLoginInterceptor.

Freeman

On 2012-2-27, at 下午9:57, Radomir Kadlec wrote:

Hi Freeman,

thanks for all the tips.

But from where shall I take username and password in the customer
interceptor for *cxfbc:provider*?
I use no customer interceptors in the *cxfbc:consumer*, so I don't save the incoming username and password anywhere. The JAAS auth module takes care for
the authentication in the consumer.

Does *JAAS* it?
Or must I create also new customer interceptor for the cxfbc:consumer to
save them temporary?

Thanks,
Radomir

--
View this message in context: 
http://servicemix.396122.n5.nabble.com/cxfbc-provider-with-WS-Security-and-previous-JAAS-authentication-tp5518767p5518967.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

---------------------------------------------
Freeman Fang

FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com









Reply via email to