[keycloak-user] Keycloak - Application Clustering with sticky session

Ariel Carrera carreraariel at gmail.com
Thu Mar 8 10:40:25 EST 2018


When you use "application.session.host" in the client's admin url, in some
environments there is no way to reach to the exact application node (with
session created) to send a logout signal.
Keycloak doesn't have inside "application.session.host" information about
port number and it is impossible to reach the exact application server node.
So... when your environment have more than one application server (wildfly,
jboss, etc) listening using port offsets... Keycloak try to reach
application.session.host (port 80) but it's not a valid endpoint.
Is there a variable available to this (something like
"application.session.port")?

Thanks,

-- 
Ariel Carrera


More information about the keycloak-user mailing list