Hi,
I did not file an issue, but instead worked around it, by using HAproxy
on the keycloak server:
- make keycloak talk to haproxy on ldaps://localhost:636
- make haproxy connect to our three ldap backend servers.
As I am using this on most of our other servers as well, so it actually
makes our config more standard, plus: haproxy keeps a log of backend
servers coming up and going down, so you know at all times what is going on.
Perhaps this solution works for you too.
Best,
MJ
On 28-11-2016 21:45, dimitrios.gkazgkas wrote:
Hello what is the status of this issue ?
Cause i can confirm during a network outage when one LDAP went down (the
first one configured in the connection URL) the Keycloak server hanged.
--
View this message in context:
http://keycloak-user.88327.x6.nabble.com/keycloak-user-multiple-ldap-serv...
Sent from the keycloak-user mailing list archive at
Nabble.com.
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user