Secondary SAML session should be destroyed when primary session is deleted
Else we can have something like that:
{quote} [Fri Jun 11 15:30:30 2010] [warn] More than one SAML session found for user coudot@linagora.com [Fri Jun 11 15:30:30 2010] [debug] CGI.pm(91): Lemonldap::NG::Portal::SharedConf: Retrieve SAML session b5038fc53956d28f40dc7bc9e4ebdf5c for user coudot@linagora.com [Fri Jun 11 15:30:30 2010] [debug] CGI.pm(91): Lemonldap::NG::Portal::SharedConf: Retrieve real session 5551c6b12c19577d836907f3306c1268 for user coudot@linagora.com [Fri Jun 11 15:30:30 2010] [info] Session 5551c6b12c19577d836907f3306c1268 isn't yet available (213.41.232.151) [Fri Jun 11 15:30:30 2010] [error] Cannot get session 5551c6b12c19577d836907f3306c1268 {quote}