Thanks for your response. A few follow-up clarification questions :
----- Original Message -----
> From: "William G. Thompson, Jr." <[email protected]>
-- snip --
> > The CAS server v3.4.11 is using a default configuration.
> >
> > I _think_ this is how it works. Please confirm/correct :
-- snip --
> > 4) the bean id="grantingTicketExpirationPolicy" (defined by default
> > in the spring-configuration/ticketExpirationPolicies.xml file) is
> > the amount of time which the TGT can go unused before it expires.
> > Is that correct?
>
> Yes, for the TimeoutExpirationPolicy, where 'unused" means hasn't
> vended a Service Ticket.
>
> You might want to look at the TicketGrantingTicketExpirationPolicy
> which provides sliding window and a hardtime out. This one is set to
> be the default in 3.5
In my default installation, in
./WEB-INF/spring-configuration/ticketExpirationPolicies.xml, I see a
commented out sample definition as follows:
<!-- sample config for new TicketGrantingTicketExpirationPolicy -->
<!-- provides both idle and hard timeouts, for instance 2 hour sliding
window with an 8 hour max lifetime
<bean id="grantingTicketExpirationPolicy"
class="org.jasig.cas.ticket.support.TicketGrantingTicketExpirationPolicy"
p:maxTimeToLiveInMilliSeconds="28800000"
p:timeToKillInMilliSeconds="7200000" />
-->
Is this what you meant? I assume maxTimeToLiveInMilliSeconds equates to
hard time-out, and timeToKillInMilliSeconds equates to idle time-out.
-- snip --
> > Thanks much,
>
> Good luck!
Thanks,
Jon
--
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-user
