Implement LDAP server functionality#420
Merged
Merged
Implement LDAP server functionality#420
Conversation
Collaborator
|
Thank you for opening a PR! I will take a look at this when I get the chance |
Collaborator
|
I have spent my free time over the past few days going though this PR and reading up on the LDAP spec. I will probably merge this in soon, though I will likely change some of the configuration options before it is released. I have been mostly testing locally with ldap-utils (ldapwhoami and ldapsearch) so further testing will need to be done with real client apps. Possibly even a LDAP Client Guides docs page similar to the OIDC App Guides page. |
Contributor
Author
|
That's great! Take all the time you need! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Added optional LDAP directory server functionality, as requested and discussed here and here.
The image now accepts new
LDAP_*environment variables to enable and configure the LDAP server.If enabled, a separate LDAP server starts on another port (
3890by default) to listen to LDAP queries.The LDAP server is currently read-only and this PR is mostly a PoC, as I'm no expert in LDAP (learned it last night) and additional functionality may be added. It tries to implement most of the common LDAP endpoints and functionality, possibly working as a full replacement for LLDAP. It supports service-account bind, user DN bind, search, compare, RootDSE discoveries, user and group entries, and membership attributes.
It only implements the LDAP endpoints functionality discussed here, allowing other services to use VoidAuth as an LDAP server. It does not implement connecting to an LDAP server and using it as a source for users/groups in VoidAuth.
Documentation was updated too. The frontend is untouched.
Changes
LDAP_ENABLED.ou=people,{LDAP_BASE_DN}.ou=groups,{LDAP_BASE_DN}.inetOrgPersonposixAccountgroupOfNamesgroupOfUniqueNamesposixGroupmemberOfmemberuniqueMembermemberUid3890in the Dockerfile.Related Tickets & Documents