Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)
Rising Star

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.

462 Views
0 Kudos
Comments
New Contributor

Hello,

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

Regards

Arullaldivakar

Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
1 of 1
Last update:
‎12-22-2016 03:09 PM
Updated by:
 
Contributors
Top Kudoed Authors