mirror of
https://github.com/dignajar/another-ldap-auth.git
synced 2026-04-26 21:55:47 +03:00
[GH-ISSUE #37] Support multiple ldap server listing to improve resiliency #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aakarshg on GitHub (Jun 30, 2021).
Original GitHub issue: https://github.com/dignajar/another-ldap-auth/issues/37
Instead of connecting to a single LDAP server and if it fails for some reason not being able to support any services, it'd be really helpful to take a list of ldap servers to connect to in case the primary one goes down, where we get the can't connect error we should fall back to the list of secondaries.
This would be similar to the listing suppoorted by nginx-ldap-auth.. https://github.com/tiagoapimenta/nginx-ldap-auth/blob/master/config.sample.yaml#L3
@dignajar commented on GitHub (Jun 30, 2021):
Yes, it is possible, I will do it when I have some time.
Are you using Another LDAP Auth in Kubernetes ?
@aakarshg commented on GitHub (Jun 30, 2021):
Thanks @dignajar and yes indeed using it kubernetes:)
@dignajar commented on GitHub (Jun 30, 2021):
Great, I'm working as well in this tool for Kubernetes, and I need some testers :D
https://github.com/dignajar/another-scheduler