Disabling Single-Sign-Out on the server side helped. Thank you. On Tue, Jul 27, 2010 at 5:14 AM, Scott Battaglia <[email protected]>wrote:
> If you're not using Single Sign Out (and you're sure of that), then your > redirection is being controlled by the application's session time out. > > > On Mon, Jul 26, 2010 at 2:34 PM, Veniamin Goldin <[email protected]>wrote: > >> Hello, >> >> We are using CAS with SPNEGO through Spring Security. CAS Client version >> is 3.1.1. >> >> After successfully signing on to some particular service, the user is able >> to work for 2 hours without any disturbance, after what the user is being >> redirected to CAS for re-authentication. >> I can not find any clear explanation of that behavior neither in >> documentation (both CAS and Spring Security), nor in source code. >> Sign-Sign-Out is not being used. I have tried to change TGT expiration >> policy, even having in mind that TGT timeout should not result >> re-authentication, however it had no effect at all. >> >> Could anybody please advice me, why we are seeing such behavior? >> >> Thanks. >> >> Veniamin >> >> -- >> 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 > > -- 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
