Hi,
in my case, the system contains multiple tomcats, each one of them runs a WAR that contains the sprin-sec-saml. so i'm not sure that the tomcat which sent the saml-request is the one to handle the saml-response. hence, i need to store the messages in a db, and not in-memory, counting on the session (like HttpSessionStorage does)...
does it sound reasonable?
is there an implementation of SAMLMessageStorage that suits read/writes from a DB?
in my case, the system contains multiple tomcats, each one of them runs a WAR that contains the sprin-sec-saml. so i'm not sure that the tomcat which sent the saml-request is the one to handle the saml-response. hence, i need to store the messages in a db, and not in-memory, counting on the session (like HttpSessionStorage does)...
does it sound reasonable?
is there an implementation of SAMLMessageStorage that suits read/writes from a DB?
