Skip to main content
krajguru
krajguru
Gold ⭐️
December 22, 2016

Issues when configuring Ranger usersync to use anonymous binds for LDAP

  • October 5, 2026 at 9:03 AM
  • 1 reply
  • 2073 views
  • Translate All

PROBLEM

When setting Bind Anonymous in Ambari's Ranger usersync tab it complains that ranger.usersync.ldap.binddn can not be empty in ambari usersync service logs, with the below stack trace :

File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py", line 44, in ranger
setup_usersync(upgrade_type=upgrade_type)
File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py", line 319, in setup_usersync
password_validation(params.ranger_usersync_ldap_ldapbindpassword)
File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py", line 249, in password_validation
raise Fail("Blank password is not allowed for Bind user. Please enter valid password.")
resource_management.core.exceptions.Fail: Blank password is not allowed for Bind user. Please enter valid password.

ROOT CAUSE :

Currently 'Bind Anonymous' option is not supported in Ranger. Hortonworks Internal BUG-68578 has been filed to disable this option in Ambari.

RESOLUTION

Use a binddn and the bind password for Ranger Usersync.

1 reply

arullaldivakar1
arullaldivakar1
Silver ⭐️
December 20, 2018

Hello,

Is there a property to add anonymous bind in the custom configuration or so ?

Regards

Arullaldivakar

Translate
Terms & ConditionsAccessibility statement