And this tested out just fine with a short load test: several iterations of
request login page from server A, POST to server B, validate on server C, for
various values of A, B and C.
Tom.
On Oct 24, 2016, at 11:41 AM, Misagh Moayyed
mailto:mmoay...@unicon.net>> wrote:
Yes and yes. Test bef
So just to confirm... does that mean that this paragraph:
There is a further consideration for active/active deployments: session
affinity. Session affinity is a feature of most load balancer equipment
where the device performs state management for incoming requests and routes
a client to t
So just to confirm... does that mean that this paragraph:
There is a further consideration for active/active deployments: session
affinity. Session affinity is a feature of most load balancer equipment
where the device performs state management for incoming requests and routes
a client to the s
Yes and yes. Test before switching.
With deprecation/removal of the login ticket ("lt") from the CAS login page
(around 4.2.6 or so), it seems login is now "stateless", in that one can now
submit the login form to a different cluster server than which generated the
login page.
Before we a
With deprecation/removal of the login ticket ("lt") from the CAS login page
(around 4.2.6 or so), it seems login is now "stateless", in that one can now
submit the login form to a different cluster server than which generated the
login page.
Before we ask to change (remove) our load balancer TL
