RANGER-5758 : Support for Openldap service for ranger usersync in ran… - #1193
RANGER-5758 : Support for Openldap service for ranger usersync in ran…#1193pushkargogte wants to merge 1 commit into
Conversation
c855ce6 to
582c8a3
Compare
582c8a3 to
33566dd
Compare
| SYNC_LDAP_USER_SEARCH_BASE = ou=People,dc=example,dc=com | ||
| SYNC_LDAP_USER_SEARCH_FILTER = (objectClass=inetOrgPerson) | ||
|
|
||
| SYNC_LDAP_GROUP_SEARCH_BASE = ou=People,dc=example,dc=com |
There was a problem hiding this comment.
That property does not exist. The correct install property is SYNC_GROUP_SEARCH_BASE; check ranger-usersync-install.properties and installprop2xml.properties
|
|
||
| SYNC_USERNAME_CASE_CONVERSION = lower | ||
| SYNC_GROUPNAME_CASE_CONVERSION = lower | ||
| LGSYNC_LDAP_LARGEGROUPSYNC_ENABLED = true |
There was a problem hiding this comment.
Both the script and doc set this, but it is not mapped in unixauthservice/scripts/templates/installprop2xml.properties. It will not reach ranger-ugsync-site.xml during setup. The runtime key is ranger.usersync.ldap.largegroupsync.
Fix: Add the mapping, or remove the setting from script and doc.
|
|
||
| ### 4.B Ranger Admin Native Properties | ||
|
|
||
| File: `ranger/dev-support/scripts/admin/ranger-admin-install-postgres.properties` |
There was a problem hiding this comment.
Correct path:
dev-support/ranger-docker/scripts/admin/...
|
|
||
| ### 4.C Ranger UserSync Native Properties | ||
|
|
||
| File: `ranger/dev-support/scripts/usersync/ranger-usersync-install.properties` |
There was a problem hiding this comment.
Correct paths:
dev-support/ranger-docker/scripts/usersync/...
| @@ -0,0 +1,206 @@ | |||
| # Containerized Apache Ranger & OpenLDAP Native Integration | |||
There was a problem hiding this comment.
Not linked from README.md
The LDAP guide is orphaned. A one-line pointer under “Run Ranger Services” would help discovery.
| image: osixia/phpldapadmin:0.9.0 | ||
| container_name: local-ldap-admin | ||
| ports: | ||
| - "8080:80" |
There was a problem hiding this comment.
phpLDAPadmin on 8080 conflicts with Trino in the full stack. Worth noting in the doc or using another host port (e.g. 8089).
| @@ -0,0 +1,216 @@ | |||
| #!/bin/bash | |||
|
|
|||
There was a problem hiding this comment.
Add license header
2 participants
…ger docker
What changes were proposed in this pull request?
This update makes it easier to test LDAP UserSync by bringing a ready-to-use OpenLDAP directory directly into the Apache Ranger Docker environment.
osixia/openldapimage.inetOrgPerson,groupOfNames, anduid).SYNC_LDAP_DELTASYNC="true"to accurately simulate how enterprise environments handle updates.How was this patch tested?
I verified this patch locally by running through a full build and deployment cycle:
mvn clean compile package installcommand.local-ldapcontainer) usingdocker-compose up -d.Testing / Setup Instructions: OpenLDAP with Ranger Docker
To verify the OpenLDAP integration with the Ranger Docker setup, please follow these steps:
1. Run the prerequisite setup script
Execute the setup script to configure the required integration settings for the Docker environment.
2. Clean up existing infrastructure
Tear down any running containers and clear dynamic volumes to ensure a clean state.
3. Boot the fresh container environment
Start the entire cluster ecosystem simultaneously in detached mode.
4. Inject directory mappings
Wait briefly for the LDAP container to initialize, then load the user/group configurations before UserSync executes its initial lookup.
5. Force UserSync discovery
Allow time for the Ranger Admin tables to finish building, then cycle the UserSync container to force discovery of the newly mapped users.