robinlin created AMBARI-11910:
---------------------------------
Summary: Problem in Ranger setup processes
Key: AMBARI-11910
URL: https://issues.apache.org/jira/browse/AMBARI-11910
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: robinlin
Hi
I found a problem in Ranger and its plugin setup processes.
After the version of 2.0, Ambari would keep the Ranger default username and
password "admin/admin" in configurations. The default account is used to create
a new administrative account in Ranger. Ambari would use new created account to
create Repositories or Policies in Ranger if the plugin is enabled.
Then every time the Ranger supported services restart, Ambari would still run
through the processes of create user and leaves a record of "admin" login in
Ranger audit. And this would make the Ranger administrator confused.
In my opinion, the default account/password might be delegated to somebody
else. Normally if the Ambari wants to access the Ranger API, it should use its
own account/password.
So how about changing to the processes below?
Step 1) Check if the account for Ambari is valid.
Step 2a) If yes, using the account/password for Ambari to access with Ranger.
Step 2b) If not, using the default account/password to run through the original
processes.
And if I may, I would like to help to modify the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
