-
-
Notifications
You must be signed in to change notification settings - Fork 164
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
David Gubler
committed
Apr 4, 2017
1 parent
42ff18e
commit 5de09ad
Showing
2 changed files
with
5 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5de09ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so yeah, everyone keeps forgetting the
attributes
keys for ldap, and they definitely don't work with this commit. I would've commented to keep this break from going to master, but I don't see a merge request anywhere with this commit in it.5de09ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give me a quick example of what doesn't work? We have three setups with LDAP, so I don't quite understand currently what the problem is.
The previous version with the YAML workaround had broken string encoding, the result was that LDAP passwords that contained a backslash didn't work.
5de09ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
disregard... i had to reformat the "strings" in my yaml, and now it works fine. 👍