Bah: http://www.nabble.com/Question-about-CAS-session-expiration-tf3065318.ht ml#a8525979
So it appears the answer to my question is that the default TimeoutExpirationPolicy is an activity-based timeout. =C If this is so, then it would be helpful if the documentation for the class actually specified this. After looking over the code where the ticketGrantingTicketExpirationPolicy is used, to create an expiration policy that is a hard expiration timeout, then you would simply have to create one that didn't update the last time the ticketGrantingTicket was used, correct? Andrew R Feller, Analyst University Information Systems 200 Fred Frey Building Louisiana State University Baton Rouge, LA, 70803 (225) 578-3737 (office) ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew R Feller Sent: Friday, December 07, 2007 3:03 PM To: Yale CAS mailing list Subject: TGT expiration policy Is CAS' TGT expiration policy based on a hard expiration date/time or is the expiration extended based upon activity? I.e. if the timeout is set to 2 hours and make a request from a CAS protected application 1 hr and 50 minutes into my 2 hour expiration, will the CASTGC expire in 10 minutes or 2 hours? Thanks, Andrew R Feller, Analyst University Information Systems 200 Fred Frey Building Louisiana State University Baton Rouge, LA, 70803 (225) 578-3737 (office)
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
