SP timing out after 60 minutes.

[MikeWho]

Yes, sounds similar to our situation - the spoken policy seemed to be at odds
with the implemented policy at the IdP. They didn't want to change the IdP
setting as it required a lengthy approval process, so requested we simply
ignore the SessionOnOrAfter setting we received instead.

In our specific case, we were able to work around this by using the
RequestMapper to 'protect' just the files which are loaded on entering the
site (initial UI, back-end session start, authentication etc.); then
anything which can be loaded dynamically later doesn't require a Shibboleth
session, so is unaffected by the timeout. Our back-end is protected
separately with a different (.Net) session. The downside is some UI elements
can be navigated to directly without a session, but that was also true
before we integrated with SAML.

It's only really feasible for us since we have a Flash-based UI where the
user is within the one 'page'; so it might not be of much help, sorry. 



--
View this message in context: http://shibboleth.1660669.n2.nabble.com/SP-timing-out-after-60-minutes-tp7584660p7585706.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.