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.

Reply via email to