On Jun 7, 2013, at 11:20 AM, DTaylor <[email protected]> wrote: > Hi Colm, > > Thank you for the information. Assuming we can get the token out, for > secure conversation do you have a suggestion of where we should store in > 2.6.2 so it can be accessed on subsequent calls? Or was this a significant > change going forward to 2.7.5?
You can see the change set at: https://fisheye6.atlassian.com/changelog/cxf?cs=1477656 It wasn't LARGE, but it did add a field to SecurityToken to hold the original SecurityContext. You could likely mimic it by creating a Map<String, SecurityContext> or something that is stored on the endpoint that would allow you to correlate the SecurityToken id with the original context. Dan > > Thanks, > > Dan > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/WS-SecureConversation-and-SAML-assertions-tp5728643p5728957.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
