The default expiration policy is an "idle" timeout I believe: http://developer.ja-sig.org/source/browse/jasig/cas3/cas-server-core/src/main/java/org/jasig/cas/ticket/support/TimeoutExpirationPolicy.java?r=1.2
We do offer other expiration policies (and you can supply your own): http://developer.ja-sig.org/source/browse/jasig/cas3/cas-server-core/src/main/java/org/jasig/cas/ticket/support Hope that helps. -Scott On 1/23/07, Tim McLaughlin <[EMAIL PROTECTED]> wrote:
Hello, I've looked through the Protocol document and the CAS 2 architecture document, and can't find the answer to this. Apologies if it is a FAQ. We are wondering if the CAS session timeout is an "idle" timeout (ie. 30 minutes from the last CAS activity for my session) or "absolute" (ie. 30 minutes from the creation of my CAS session). Thanks, Tim _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
