ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19087) Clean up how dfs.cluster.administrators is handled wrt user/group creation
Date Mon, 05 Dec 2016 15:35:59 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Onischuk updated AMBARI-19087:
-------------------------------------
    Attachment: AMBARI-19087.patch

> 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)

Mime
View raw message