RE: Two wsse:UsernameToken in a request with different wsse:Username

[Andrei Shakirin <as...@talend.com>]

Hi,

Could you try to create a new client proxy per web request (not share proxy between different web requests) and see that effect disappears or not?

Regards,
Andrei.

> -----Original Message-----
> From: patch_78 [mailto:patch_78@hotmail.com]
> Sent: Sonntag, 31. August 2014 20:52
> To: users@cxf.apache.org
> Subject: RE: Two wsse:UsernameToken in a request with different
> wsse:Username
> 
> Hi,
> 
> FYI my client will get a usernametoken from STS before sending request to WSP
> according to the policy. There is one thing I can notice is in the client
> CallbackHandler.handle which is called before sending request to the STS.
> 
> WSPasswordCallback pc = (WSPasswordCallback) callbacks[i]; pc.getIdentifier();
> ---> This is always the first user login.
> 
> Even this setting is occured before the client CallbackHandler.handle
> 
> ((BindingProvider) port).getRequestContext().put("ws-security.username",
> "CURRENT USER ID");
> 
> Any suggestions?
> 
> regards,
> Patcharee
> 
> 
> 
> 
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Two-wsse-
> UsernameToken-in-a-request-with-different-wsse-Username-
> tp5748229p5748322.html
> Sent from the cxf-user mailing list archive at Nabble.com.

RE: Two wsse:UsernameToken in a request with different wsse:Username

[patch_78 <pa...@hotmail.com>]

Actually I got the problem because only one SBIClient had been used for all
requests. After I used SBIClient for each user session, the problem was
gone.

Thanks for your reply.




--
View this message in context: http://cxf.547215.n5.nabble.com/Two-wsse-UsernameToken-in-a-request-with-different-wsse-Username-tp5748229p5749137.html
Sent from the cxf-user mailing list archive at Nabble.com.