How does session failover occur for a request?
After authentication, an internal algorithm determines the Access Manager servers (primary, secondary, tertiary, and so forth) for a user session. The Access Manager server on which the user session was created is one of those servers. If the primary Access Manager server goes down, the server at which the session request landed determines which other server services the request and forwards the request there. Note that if the session request lands on the secondary server, no forwarding occurs. The secondary server then retrieves the user session from sessiondb and services the request. The original server at which the request landed serves as a proxy for the request. The above process occurs even if the load-balancing cookie is set and the Load Balancer has forwarded the request to the Access Manager server according to the cookie’s value. When the primary Access Manager server is up and running again, it continues to service the requests for the sessions it originated. Concurrently,
