Repository navigation
RANGER-5879: Adding the docker based OpenLDAP for UserSync - #1376
Draft
krishnamuttevi wants to merge 1 commit into
Draft
krishnamuttevi wants to merge 1 commit into
krishnamuttevi wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
UserSync LDAP and delta-sync behavior (including server-type-specific filters) is hard to validate without a real directory. Unit tests mock LDAP but do not cover end-to-end sync into Ranger Admin.
Solution
Dev-support
Add .yml with local-ldap (and optional phpLDAPadmin) on the rangernw network.
Add .ldif with a minimal DIT (ldapuser1, group engineering) suited to inetOrgPerson / groupOfNames and group search.
Add .sh to seed LDAP and, when requested, point UserSync at local-ldap, optionally enable Admin LDAP auth, and restart ranger-usersync / ranger.
Document the flow: bring up Ranger core plus LDAP compose file, then run the connect script (LDAP remains opt-in so default dev workflows stay on Unix sync).
Functional tests (planned / in progress)
Extend functional-tests/run-tests.sh with optional container ldap and suite ldapusersync.
Add functional-tests/ldapusersync/ for assertions against Admin REST and UserSync logs (synced user/group, LDAP source, delta filter lines for ldap server type).
Gate LDAP suites on env (e.g. ENABLE_LDAP_SYNC=true / SELECTED_CONTAINERS=ldap) so CI and local runs without LDAP are unchanged.