We've had this happen with bad clients that fail to recognize the ticket in certain situations, as well, for example:
Browser < I'm here to use your app Bad CAS Client > You have no session, see the cas server and come back with a ticket < Here's my ticket - ST... > You have no session, see the cas server and come back with a ticket < Here's my ticket - ST... & ST... > You have no session, see the cas server and come back with a ticket < Here's my ticket - ST... & ST... & ST... > You have no session, see the cas server and come back with a ticket < Here's my ticket - ST... & ST... & ST... & ST... > You have no session, see the cas server and come back with a ticket < Here's my ticket - ST... & ST... & ST... & ST... & ST... ... continues until the user notices their browser is hung (due to infinite redirects back to cas server) and closes it. On Dec 8, 2010, at 10:50 AM, Dean Heisey wrote: > > This started happening to me as well ..just to be sure I understand what the > fix should be: > > You either set redirectAfterValidation and useSession to false in the > client > > OR > > enable sticky sessions in the load balancer? > > > Dean > -- > View this message in context: > http://jasig.275507.n4.nabble.com/Re-CAS-infinite-redirect-loop-tp584495p3078804.html > Sent from the CAS Users mailing list archive at Nabble.com. > > -- > 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
