Hello team, I've implemented CAS fail over with the help of database backed ticketRegistry and dns fail over . Now, at the time of transition from secondary to primary server if the primary server I got ticket not recognized error. The exact scenario is like this: I opened one browser while being at secondary server and started the primary CAS server, then dns will point to primary server. Then in the previously opened browser (browser opened in secondary server instance), I provide the valid credentials which is successfully authenticated and redirected to requested product. In the product landing page I got ticket not recognized error. I think while logging in secondary server issued the ticket and validation request goes to primary server. Do we have any resolution for this? Also, refreshing the browser of resending the request to the product does not solve the problem. I have to close the browser and re open it (really unacceptable). If this could not be resolved completely, can not we just make the ticket validation failure to make sure that next ticket is generated in the next request so that refreshing the page or resending the request will solve the issue?
Regards, Lekhnath PRIVACY NOTICE This email and any attachments may be confidential and/or privileged. Use of the information contained in this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and delete this email. -- 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-dev
