Hi Dan, It should be possible, although I haven't tried it in the context of Secure Conversation. Once the security header has been processed as per WSS4JInInterceptor, then you have full access to the security results from the message context.
Colm. On Thu, Jun 6, 2013 at 4:33 PM, DTaylor <dan.tay...@merge.com> wrote: > Hi Colm, > > Sorry I got myself turned around yesterday and have since removed the SC > policy from the STS and have things working now. There was a modification > we had made on our end which was causing the problem I was seeing. > > Do you know if for 2.6.2 we can put an interceptor into the interceptor > chain to capture the incoming SAML token? Specifically would it have to be > before the SC interceptor or after? I ask because although we do want to > move to 2.7.5, we need to verify backwards compatibility on a move to 2.7.5 > and may not have time to do so in this release, where we really need to get > SC working. > > Thanks, > > Dan > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/WS-SecureConversation-and-SAML-assertions-tp5728643p5728857.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
