On Fri, Feb 11, 2011 at 18:49, Jean Alex Jean Louis philippe
wrote:
> Thank you for your reply.
>
> I understand your answer. However this means that from a system standpoint,
> it is impossible to have an idle timeout when using CAS because CAS will
> automatically send a logout service ...!
>
Thank you for your reply.
I understand your answer. However this means that from a system standpoint, it
is impossible to have an idle timeout when using CAS because CAS will
automatically send a logout service ...!
My question is: Is there any solution to meet this need?
I thought about chan
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 ser
