This policy: https://source.jasig.org/cas3/tags/cas-server-3.4.2.1/cas-server-core/src/main/java/org/jasig/cas/ticket/support/MultiTimeUseOrTimeoutExpirationPolicy.java
gives you 60 minutes (or whatever time you pick) between each service access. That's the best we have. We don't currently allow pingbacks to the server to extend sessions (it would require some unique identifier between service and server in order to identify the service since we don't share the TGT with services) On Wed, Sep 1, 2010 at 1:10 PM, Venka Ashtakala <[email protected]>wrote: > > The system we are implementing is supposed to have a 60 minute inactivity > timeout, so, I've set a 60 minute timeout in the ticketExpirationPolicy.xml > in the grantingTicketExpirationPolicy bean. As I understand it, if the > ticket granting ticket is not used for 60 minutes then it times out. > > However, lets say a user authenticates and is using a client application > for more then 60 minutes, this means that the granting ticket would have > expired without the user's knowledge, even though the user has been using > one of the client apps. > > Is there a way to setup the CAS client to 'ping' in some manner the CAS > server so that while the client app is being actively used, it indicates to > the CAS server to NOT timout the granting ticket? > > -- > 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 > > -- 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
