Krishna Chaitanya Muttevi created RANGER-5879:
-------------------------------------------------

             Summary: Add docker based OpenLDAP for UserSync dev testing and 
functional-test integration
                 Key: RANGER-5879
                 URL: https://issues.apache.org/jira/browse/RANGER-5879
             Project: Ranger
          Issue Type: New Feature
          Components: Ranger, usersync
            Reporter: Krishna Chaitanya Muttevi


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. The existing Docker stack defaults to 
Unix UserSync and PAM Admin login.
h3. 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.

 



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to