Hi Freddy, Where exactly in the code is the SecurityToken being inserted into the TokenStore? I fixed an issue recently to avoid storing IssuedTokens in the cache on the service side that may help you:
https://issues.apache.org/jira/browse/CXF-5584 Aside from that, could you explain where the method name/parameters/etc are actually being stored in the SecurityToken object? I'm not familiar off-hand with anywhere that this is done. Colm. On Fri, Feb 28, 2014 at 9:26 PM, Freddy Exposito <[email protected]> wrote: > Hi All, > > It's happening to us that the SecurityToken representing a SAML Token in > the > service side is being created (and saved in the TokenStore) with references > to the method name, parameters, etc of the web service that was called. > It's > even including the parameters values in the TokenStore. > > Is this an expected behavior? Maybe there is something in the configuration > to avoid this or we are doing something wrong? > > The web services we are using are to store images so the token store size > grows a lot due to this. > > 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-tp5740668.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
