Hi Anthony, Yes, passing security token through ThreadLocal is a possible solution that don't affect the service implementation code. However, it works only in case if your service A implementation calls the service B in the same thread. Otherwise you need to update service implementation.
Regards, Andrei. > -----Original Message----- > From: Anthony Fryer [mailto:[email protected]] > Sent: Montag, 26. Oktober 2015 04:34 > To: [email protected] > Subject: RE: service calling another service, passing the same security header > > Hi Andrei, > > Thanks for your response. I didn't know the UT could be get/set that way. > Ideally though i'd prefer not to have to code this logic into the actual > service > implementation and use interceptors to do this. Maybe i could set the token > in > a ThreadLocal in the in interceptor and then reuse that in the out > interceptor? > > Cheers, > > Anthony > > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/service-calling- > another-service-passing-the-same-security-header-tp5762028p5762237.html > Sent from the cxf-user mailing list archive at Nabble.com.
