-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ldap: missing default values make configuration difficult #59
Comments
Oh, never mind. The clue is all fields in the ldap: section must be there; otherwise, the config is wrong.. |
Actually, that's pretty sucky for users, so I'm reopening this to rework that. You're not the first person to be bitten by this. |
I did get it to work with anonymous access, and that's not documented either in the docker page.. |
What did you need to do to enable anonymous access? Set the field to the empty string? |
I should add this is mostly a duplicate of #41 aside from the anonymous access question. |
This is what worked; but yes, both binddn and bindpw have to be defined, and empty - aka ''
|
Thanks, I'll get a documentation tweak into the README that says that. |
I've just released version 4.0.1 of this chart which resolves this issue. |
You have to set a password for the ldap access.. in anonymous access, there is no need for a read-only connection to have a password. This is the mode we run our ldap service as.
The chart errors out at:
The text was updated successfully, but these errors were encountered: