If failover occurs between Dist-Auth servers during authentication, is the LB cookie reset?
If the primary Dist-Auth server for the request fails after the GET operation to the Access Manager server, the load balancer sends the request to another Dist-Auth server, which then reinitiates the authentication request and resets the lbcookie value to that configured for the secondary server. After successful authentication, the lbcookie value, which becomes the one that’s configured for the Dist-Auth server that successfully authenticated the user, remains unchanged for the lifetime of the session. This process is transparent to the user, who is not prompted to log in again after the primary Dist-Auth server fails.
