Sessions are only bound to the server that they originated from unless you replicate them across your web farm. But that's a general issue and not CAS specific. You'll find that anything you put in your session wouldn't have been replicated to other servers.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Thu, Dec 11, 2008 at 10:08 AM, Arthur Erdös <[EMAIL PROTECTED]> wrote: > Hello NG, > > I've noticed a strange problem with CAS concerning a WebApp using load > balancing. The isAuthenticated() method seems to return false when the > load balancer sends the user to another webserver although he is really > logged in and authenticated at CAS... > > The error only occurs when the load balancer is configured to send the > user randomized to an available server. It does NOT occur when it is > configured to send the user (session) always to the same server! > > Has anybody noticed such a behavior? Is this a known issue? Is the SSO > session bound to the server the login request came from? > > Thx in advance for the hints ;) > > best regards > Arthur > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
