-
Notifications
You must be signed in to change notification settings - Fork 90
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
Passing unicode parameters to LDAP library #168
Comments
Probably means that your LDAP configuration is not working. Which version of realms-wiki are you using? |
I have verified my LDAP setup using
It works and returns all the objects in "ou=people,dc=example,dc=com" Using the same credential in realms-wiki.json:
I have verified my credentials on other ldap services and they are correct. I have tried both the username and the complete email address as the login but no luck. |
see https://github.com/ContinuumIO/flask-ldap-login/blob/master/examples/bind_search.py but there is no 'USER_SEARCH' option to tell the ldap client where to find the users. maybe
|
A million thanks @stephane-martin! LDAP is working fine now. STARTTLS too. But now the editor broke :( I will use the relevant issue (#169) for that. |
yes it's better to expose realms at the root of the domain, some things break when you try to install in /somesubdir |
by the way i have a current pull request to get rid of flask-ldap-login, so that LDAP authentication becomes python3 compatible. expect LDAP configuration to change a bit in future versions. |
That would be great! I spent endless hours trying to figure out what's going on and this will ease the pain in future deployments :). |
Hello,
the LDAP parameters come from a JSON file, so in python 2 they are parsed as "unicode" strings. The LDAP library that realms use for LDAP auth does not accept unicode for parameter names :(
Please see: ContinuumIO/flask-ldap-login#26
The text was updated successfully, but these errors were encountered: