Ryan explained it quite well. If you want your SSO session to be longer you don't want to touch the container session as that won't do anything.
Cheers, Scott On Tue, Oct 6, 2009 at 4:21 PM, Ryan Fox <[email protected]> wrote: > > ----- "Joe Hansen" <[email protected]> wrote: > > > WoW! Thanks for the quick reply, Scott! > > > > I increased the session-timeout for the CAS webapp precisely for the > > same reason (i.e. The user should be able to spend 4 hours on a form > > before he hits the submit button). > > Actually.. there's still a misunderstanding. The timeout you changed > affects how long a user can take to complete the cas login process. For a > default configuration.. 5 minutes is likely plenty. A user is shown the > login form, and has 5 minutes to hit submit. If they don't within that time > period, CAS assumes the session is abandoned and shows a fresh login screen > at next request. > > You want to change the timeout for a ticket that is granted, so that a user > is not timed out of a casified application in the middle of doing something. > This is common, and easily configured in CAS. See > http://www.ja-sig.org/wiki/display/CASUM/Ticket+Expiration+Policy . > > Thanks, > Ryan > > -- > > Ryan Fox > The University of Findlay > 1000 N Main St - Findlay, OH 45840 > 419-434-4348 > > -- > 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
