TGT expiration policy

[Scott Battaglia]

On Dec 7, 2007 4:32 PM, Andrew R Feller <afelle1 at lsu.edu> wrote:

>  Sorry, I wasn't thinking when I replied.  By extending the isExpired()
> implementation, I would need to compare the creation time of the ticket
> against the system's current time and expire it after a time specified in
> the constructor.
>
You'll merely need to implement an ExpirationPolicy that does what you need
(in your case yet comparing the creation time to the current time).

>
>
> Scott: If you want this included back into the source distribution, I will
> send it to you.
>
We're always willing to accept contributions :-)

Thanks
-Scott


>
>
> Andrew R Feller, Analyst
>
> University Information Systems
>
> 200 Fred Frey Building
>
> Louisiana State University
>
> Baton Rouge, LA, 70803
>
> (225) 578-3737 (office)
>   ------------------------------
>
> *From:* cas-bounces at tp.its.yale.edu [mailto:cas-bounces at tp.its.yale.edu] *On
> Behalf Of *Andrew R Feller
> *Sent:* Friday, December 07, 2007 3:13 PM
> *To:* Yale CAS mailing list
> *Subject:* RE: TGT expiration policy
>
>
>
> Bah:
> http://www.nabble.com/Question-about-CAS-session-expiration-tf3065318.html#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:* cas-bounces at tp.its.yale.edu [mailto:cas-bounces at tp.its.yale.edu] *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
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>


-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20071211/85a9fabc/attachment.html