Hi, 

I'm running an keycloak cluster behind haproxy. 
Keycloak sets its own session cookie as AUTH_SESSION_ID with value 
<session-id>.<owner-node-id>. 
The owner-node-id represents the node that "owns" the session. 
This node may not be the node that the client connects to, but connecting to it 
is recommended for performances. 

Thus, the initial connection could reach node1, the sessions assigned to node2 
and haproxy will then stick to node1 whereas it would be optimal to stick to 
node2. 

Is there a way for haproxy to stick to a value extracted from a cookie returned 
by the server, without adding its own stickness informations ? 

Thanks, 
Ionel 

--
232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON
Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301

Reply via email to