-
Notifications
You must be signed in to change notification settings - Fork 56
Allowance of variables in "bind_dn" and "password" field. #23
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
Comments
Hey, RaVoR. The plugin wraps omniauth-ldap. Looks like they have an outstanding issue to support binding against the current user: omniauth/omniauth-ldap#59. In short, we would need them to support this behavior in order for this plugin to have a hook to bind the current user. Take care, |
@jonmbake info: backtrace:
env:
|
ok sorry, i had some ldap settings wrong, seems like its working now with correct ldap bind dn and so on :) |
Hey there,
first I want to mention, thats great, that you guys did implement such a function for Discourse.
I found myself playing around with this and found, that you need a bind_dn if anonymous access to LDAP isn't allowed. In another application of me, I simply use the Loginname (userPrincipalName) as bind_dn. I tried to to that with your plugin, but no avail. Is it possible to have variable-names within the base_dn or password-field, so the values typed in are used instead of fixed values?
BR,
RaVoR
The text was updated successfully, but these errors were encountered: