-
Notifications
You must be signed in to change notification settings - Fork 0
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 LDAP authentication #144
Comments
Druid already supports LDAP authentication https://druid.apache.org/docs/latest/operations/auth-ldap.html Edit: I meant by this that at least we don't have to write an extension for it - we just need to configure it properly |
Blocked by #6 |
Blocked by #365 |
The first PR #374 is in review now. To close this ticket, we'll need to add ldaps:// in a later PR. They are separated for the sake of reviewer convenience, as the second part will require refactoring TLS-related code as well. |
Follow-up tickets from the initial LDAP feature implementation PR, to be prioritized: |
# Description This will resolve part of #144 The ticket can be merged once the stretch goals are reached as well. A new iteration on the changes prototyped in #341 This iteration will include: * A closer resemblance to the ticket requirements - using a list of authenticators * Non-usage of LDAP for inter-node authentication (basic authentication instead) * Erroring out if both TLS auth and LDAP auth are configured ## Follow-up Work * Interconnection with an OPA authorization config, if provided (former stretch goal) * Adding ldaps:// support (former stretch goal) * Druid does not like anonymous LDAP access (without bind credentials). I have not found a way to configure it. This however, seems to be a usecase we want to support generally.
I briefly talked to Vladislav today and he said that we might want to do more work here before we finish this ticket. |
My current understanding: there is the intention to add ldaps support to this ticket before closing it. The consensus was, that it probably would not be a lot of effort and supporting ldaps is something people expect. The previous PR was very long-running and already quite big, which is why I opted to close it instead of cramming #382 into it as well. Adding ldaps could turn out to be a relatively simple PR, but from what I could tell a lot of existing TLS functionality would need to be adjusted as well (creating and handling a common trust store mostly), making it seem larger than it is. |
As a user I'd like to use my existing LDAP/AD credentials to log into Druid. This was already done in e.g. NiFi or Trino. This can be especially helpful for writing tests.
The LDAP support should be integrated in the structure from PR #6 which must be finished first.
This is done when
This depends on the reference architecture developed in stackabletech/issues#170
The text was updated successfully, but these errors were encountered: