Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

How can the Ambari Ranger Admin internal user (amb_ranger_admin) be force recreated in Ranger?

avatar
Contributor

When installing an existing Ranger 0.4 into Ambari 2.2 to facilitate management in Ambari, the amb_ranger_admin user was not created in Ranger.

What is the simplest way to force this account to be generated?

1 ACCEPTED SOLUTION

avatar
Contributor

Thanks to support we determined the problem to be either an incorrect/unset password for the Ranger admin user or HDFS needing to be restarted after enabling the plugin. One or both of these two things solved the problem.

View solution in original post

10 REPLIES 10

avatar
Master Mentor

@Erik Nor

This may help to clarify the question. I don't remember creating this user manually

http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.4/bk_Ranger_Install_Guide/content/updating_ran...

avatar
Master Mentor

Its created in my case

1460-screen-shot-2016-01-19-at-104833-am.png

avatar
Contributor

The amb_ranger_admin internal user as shown above is not present in Ranger Admin.

avatar
Master Mentor

@Erik Nor It should if install went fine. Try searching again ...Is ranger working fine? Try restarting the service

1463-screen-shot-2016-01-19-at-105433-am.png

avatar
Master Mentor
@Erik Nor

Have you enabled any plugin? Try enabling the plugin to see if it creates the user or not

avatar
Contributor

Yes, the HDFS plugin is enabled. The user still doesn't exist.

avatar
Master Mentor

1464-screen-shot-2016-01-19-at-110618-am.png

Looking at the explanation of the property and looks like used needs to be there to create repo and policies.

avatar
Contributor

To clarify, the account and password are correctly defined in Ambari, but they do not exist in Ranger Admin.

avatar
Contributor

Thanks to support we determined the problem to be either an incorrect/unset password for the Ranger admin user or HDFS needing to be restarted after enabling the plugin. One or both of these two things solved the problem.