-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
support for ldap for user storage #28
Comments
Hey thanks for your feedback, I think integrations like LDAP, OpenID and SAML/JWT Assertions are important for the project's success. I have not a clear roadmap yet when to get there but I'm happy for any input, ideas or contributions regarding that matter. |
You could easily implement LDAP for user storage by introducing a new connector (they are called providers right now see #38). The interface can be found here with an example implementation here. Please be aware that the Provider interface is not final and is subject to change to make things more compatible with non-OAuth2 providers. Additionally, Providers will be renamed to Connectors which is tracked in #38 |
thanks for the hint, I think I will have time to look on it in 4~5 weeks, I will tell you if I start to write actual code so that tobe sure things integrate nicely :) |
👍 :) |
with #62 hydra has a new identity workflow. you can now implement LDAP easily |
I don't know how to handle that in a nice and microservice way (have hydra to connect to 3rd-party user provider, that all must fullfil a http api contract, so that any body can implement his user provider and it will connect nicely with hydra, without needing to have that in hydra itself ?)
But as this tool is aim for corporate scenario, and a lot of company do store their user in LDAP, hence being able to get the user from there would IMHO greatly the places where hydra would be relavant.
The text was updated successfully, but these errors were encountered: