[
https://issues.apache.org/jira/browse/AMBARI-19087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732108#comment-15732108
]
Hudson commented on AMBARI-19087:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6185 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6185/])
AMBARI-19087. Clean up how dfs.cluster.administrators is handled wrt (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c4728f2f71f899ca1be98da0a85bdfcb514e07c8])
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-site.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py
> Clean up how dfs.cluster.administrators is handled wrt user/group creation
> --------------------------------------------------------------------------
>
> Key: AMBARI-19087
> URL: https://issues.apache.org/jira/browse/AMBARI-19087
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19087.patch
>
>
> dfs.cluster.administrators handles values of the following format:
>
>
> CL for the admins, this configuration is used to control who can access
> the default servlets in the namenode, etc. The value should be a comma
> separated list of users and groups. The user list comes first and is
> separated by a space followed by the group list, e.g. "user1,user2
> group1,group2". Both users and groups are optional, so "user1", " group1",
> "", "user1 group1", "user1,user2 group1,group2" are all valid (note the
> leading space in " group1"). '*' grants access to all users and groups, e.g.
> '*', '* ' and ' *' are all valid.
>
> Ambari cannot handle * value correctly it will try to create a group or user
> named '*'.
> Also Ambari cannot correctly create groups if there are multiple spaces
> instead of one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
