CAS timeouts only apply to the single sign on session at the server level. CAS expiration policies tend to fall in some combination of three categories (time to idle, time to live, and # of uses). Time to idle is time in between ticket uses. Not the amount of time you've been actively using a service.
On Thu, Feb 10, 2011 at 10:50 AM, Jean Alex Jean Louis philippe < [email protected]> wrote: > Hello, > I do not know if this is the right place to submit my request ... I have > a problem concerning the definition of the CAS IdleTimeout. > > I want to be able to expire the session of a CASified service after 30 min > of inactivity in this service. Due to a problem caused by the way Spring > implements the Concurrent Session management, the timeout of the service is > set to 5 min (in the web.xml file of the service). But, if the service is > loaded for more than 30 min, CAS send a logout request to it and at the next > request, even if the user is not idle, he is kicked out. > > For the point of view of a user (that doesn't know that he is in a system > and not in a single WEB application, that's not acceptable). > > Question: Does it exist a way to control the idle session timeout from CAS > server even if the session timeout does not occur yet in the service. > > Thanks! > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
