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

Hudson commented on AMBARI-13177:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #594 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/594/])
AMBARI-13177. Ranger setup does not respect custom service users (Gautam Borad 
via smohanty) (smohanty: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b01b0da303544edcef13bd454b47ae4129c45d01)
* ambari-server/src/test/python/stacks/2.2/RANGER/test_ranger_usersync.py
* 
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
* ambari-server/src/test/python/stacks/2.2/RANGER/test_ranger_admin.py
* 
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py


> For HDP 2.2: Ranger setup does not respect custom service users
> ---------------------------------------------------------------
>
>                 Key: AMBARI-13177
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13177
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13177.1.patch, AMBARI-13177.patch
>
>
> PROBLEM: In an Ambari install it's possible to use different user accounts 
> for service users, such as the hive user and the hdfs user. 
> The plugin enable scripts set the owner of various component specific files 
> such as the jceks files. When the services use custom users, the ranger 
> scripts still set the owner of the files to the "standard user", resulting in 
> permissions problems. 
> For example if I make my hive user "special-hive-user", the ranger scripts 
> still will set the owner to "hive".
> The ranger scripts need to use the information in Ambari for the custom 
> service users and propagate this to the setup scripts.



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

Reply via email to