[ 
https://issues.apache.org/jira/browse/AMBARI-10507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497155#comment-14497155
 ] 

Hudson commented on AMBARI-10507:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2327 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/2327/])
AMBARI-10507. Local root user's group being assigned to hadoop. (Adam Westerman 
via yusaku) (yusaku: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b58969228db8a34fb1c3c8a249b8691bf83bce21)
* 
ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/admin-properties.xml


> Local root user's group being assigned to hadoop
> ------------------------------------------------
>
>                 Key: AMBARI-10507
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10507
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server, security
>    Affects Versions: 2.0.0
>            Reporter: Adam Westerman
>            Assignee: Adam Westerman
>            Priority: Critical
>              Labels: patch, security
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10507.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When installing Ranger through Ambari, you have the option to specify DB user 
> names. If you leave the Ranger DB root user configuration db_root_user as the 
> default (which is 'root'), Ambari will erroneously attempt to create a local 
> user named root, and assign it to the group 'hadoop'.  This results in local 
> root users being reassigned to the group 'hadoop'.  In addition, both the 
> db_user param and audit_db_name param are erroneously being used to create 
> local users (granted, with less severe consequences).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to