Hi, Rangerusersync is only in Ranger ADMIN not UNIX.
Our HADOOP is kerberized but I don’t see how that affects ranger connecting to LDAP to gather users and group information. I have tested the LDAP parameters with a command-line ldapsearch and have success but the lack of results within usersync is a mystery, and the lack of a clear error does not help. From: Loïc CHANEL <loic.cha...@telecomnancy.net> Sent: Tuesday, June 11, 2024 2:41 PM To: user@ranger.apache.org Subject: Re: No usersync EXTERNAL Hi Marc, If rangerusersync Unix user exists, then you may want to modify the unix_user and unix_group in install.properties to adapt to your case. Now for Kerberos, this applies only if you are in a kerberised environment. Otherwise you leave this blank. Best regards, Loïc Le mar. 11 juin 2024 à 14:28, Marc Hoppins <marc.hopp...@eset.com<mailto:marc.hopp...@eset.com>> a écrit : Hi all, Sorry to appear dumb but am still trying to get this working. Why does install.properties have: #User and group for the usersync process unix_user=ranger unix_group=ranger If the rangerusersync ID exists? #change password of rangerusersync user. Please note that this password should be as per rangerusersync user in ranger rangerUsersync_password= and KERBEROS #Set to run in kerberos environment usersync_principal= usersync_keytab= hadoop_conf=/etc/hadoop/conf What does HADOOP Kerberos have to do with LDAP – our LDAP is active directory. Marc Hoppins
