Hi Dan, > I am unable to get any of the Claims, the Principal or anything else that is > on this token.
Can you access your claims via token DOM element: Element tokenElement = token.getToken(); ? Complete XML representation should be available there. You can try to put HTTP tracer between client and STS and examine received token. > The SecurityContext is still null as well The SecurityContext will be initialized on recipient side, no initiator side. Regards, Andrei. -----Original Message----- From: DTaylor [mailto:[email protected]] Sent: 14 May 2012 23:36 To: [email protected] Subject: RE: Accessing Claims in a client Hi Andrei, Thank you for the additional help. I've been able to get this token, however I am unable to get any of the Claims, the Principal or anything else that is on this token. When I remove the claim processor from the STS, the client cannot access the service (as expected). When I access the SecurityToken from the TokenStore in the EndpointInfo there is no Principal (null value returned). There is only one token in the TokenStore. There is also no TOKEN_ID stored as a contextualProperty in the message. The SecurityContext is still null as well. I'll be running the client through the Eclipse debugger tonight / tomorrow to provide more information. Thank you again for all of the help you've given Andrei & Colm. It is much appreciated. Dan -- View this message in context: http://cxf.547215.n5.nabble.com/Accessing-Claims-in-a-client-tp5698187p5707852.html Sent from the cxf-user mailing list archive at Nabble.com.
