-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
connectors: LDAP #119
Comments
Yes! This is something we're very interested in doing, but no work has begun on this feature yet. If you can add more details about what sort of integration features you'd like that would be helpful for whoever picks this up. |
here's a list of configuration options needed for a read-only connector, without group support:
for password change we might need:
if registration should be supported, it gets more complicated because the whole LDAP object needs to be created, which includes construction of the DN and all attributes. |
The first step here would be for someone to provide an example configuration of openldap with some users and groups. That would give someone less familiar with ldap a starting point. |
I have a LDAP Connector in the works. It is not quite ready yet, but I would really like initial feedback/reviews nontheless. Please have a look at #178 |
@fnordahl Nice! I would love to have an example kubernetes setup with openldap that we could test against too. |
@philips I have linked to a openldap Docker image that may be usefull and wrote some notes in a comment on the PR. Let me know if there is anything else I can provide/help with. |
Authentication is performed by binding to the configured LDAP server using the user supplied credentials. Successfull bind equals authenticated user. Optionally the connector can be configured to search before authentication. The entryDN found will be used to bind to the LDAP server. This feature must be enabled to get supplementary information from the directory (ID, Name, Email). This feature can also be used to limit access to the service. Example use case: Allow your users to log in with e-mail address instead of the identification string in your DNs (typically username). To make re-use of HTTP form handling code from the Local connector possible: - Implemented IdentityProvider interface - Moved the re-used functions to login_local.go Fixes dexidp#119
Being able to proxy requests to a LDAP is useful.
I would love an even semi-working implementation.
This feature was mentioned in the announcement.
The text was updated successfully, but these errors were encountered: