Thanks. There is a bug that the token wasn't cloned in a particular method - I'll fix this imminently.
Colm. On Wed, Mar 12, 2014 at 1:49 PM, Freddy Exposito <[email protected]> wrote: > Hi Colm, > > I tried with 2.7.11-SNAPSHOT and we are not having the issue anymore so it > seems that CXF-5584 fixed it for us. > > It was happening in 2.7.10 in the > IssuedTokenInterceptorProvider. IssuedTokenInInterceptor.parseHandleResults > () > 'getTokenStore(message).add(token);' > > This is the path to the method name and parameter of the web service > invoked. > > (org.apache.cxf.ws.security.tokenstore.SecurityToken) > .token(com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl) > .ownerDocument(com.sun.xml.internal.messaging.saaj.soap.SOAPDocumentImpl) > > .firstChild(com.sun.xml.internal.messaging.saaj.soap.ver1_2.Envelope1_2Impl) > .body(com.sun.xml.internal.messaging.saaj.soap.ver1_2.Body1_2Impl) > .firstChild(com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl, > method name goes here) > .firstChild(com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl, > parameter here) > > Thanks, > Freddy > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/SAML-Token-saving-parameter-values-in-the-service-side-in-the-token-store-tp5740668p5741160.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
