Hi Team, We are using GLUU 3.1.1 in clustering mode using AWS ELB as Load balancer. Initially when we did the setup , we were getting error page when trying to access the GLUU Admin login console. when we added session stickiness , i.e for 'x' time interval all the requests from client IP Address will be served by one particular node. The GLuu Admin console was opening and we were able to login to the console. The requests were getting load balanced between either of the nodes. Reference guide used for setting GLUU clustering https://gluu.org/docs/ce/3.1.1/installation-guide/cluster/ Please provide clarity for following: 1. Does clustering includes session replication between both GLUU nodes ? For scenario , Say we have session stickiness defined as 20 seconds.The request comes on node 1 and user gets authentication done and desired operation is performed. Now after 20 seconds , the request can either go to node 1 or node 2. If the request node 2 , do we need authentication to performed again or the authentication done before will work. 2. What we talk about replication what all things are covered ? User configuration only or all session as well ? please elaborate things covered as a part of replication 3. By Saying Load balanced setup , do we mean LB or FT based setup ? LB : Using Round robin or any Algo which sends requests across both nodes ( 1 and 2 ) FT ( Active/Passive ) : We have two nodes 1 & 2. All the requests route to node1 ( active node ). When node1 goes down node2 becomes active( passive node ).