premature session removal

[Cantor, Scott]

On 4/18/12 5:42 AM, "Wolter Lier" <Wolter.Lier at planonsoftware.com> wrote:

>In our SP config we¹ve added these session cache settings which should
>provide for 8h session timeout, as far as I know:

And a sizeable waste of memory. It makes no sense to buffer sessions in
Apache that long, and the cacheAllowance is the amount to add *on top* of
the session's lifetime.

>In the Shibboleth log we find this:
> 
>2012-04-16 17:54:13 DEBUG Shibboleth.Listener [21]: dispatching message
>(remove::StorageService::SessionCache)
>2012-04-16 17:54:13 INFO Shibboleth.SessionCache [21]: removed session
>(_bd62a4c2b1ca2bf3667c90d2baca717f)
>2012-04-16 17:54:13 DEBUG Shibboleth.Listener [21]: dispatching message
>(US3245A/Login::run::SAML2SI)
> Why is the session removed at 2012-04-16 17:54:13, while some 15 minutes
>before its expiration was updated to 8 hours later?

That's not a timeout, it's an explicit logout or a problem validating the
session, probably due to IP address issues. The other log may have more
information, the remove operation is being triggered from the module, not
shibd.

-- Scott