[
https://issues.apache.org/jira/browse/AMBARI-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043359#comment-15043359
]
Hadoop QA commented on AMBARI-14228:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12775928/AMBARI-14228_branch-2.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/files.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4502//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4502//console
This message is automatically generated.
> Ambari Files View ignores alternate HDFS authorization mechanisms
> -----------------------------------------------------------------
>
> Key: AMBARI-14228
> URL: https://issues.apache.org/jira/browse/AMBARI-14228
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.2
> Reporter: DIPAYAN BHOWMICK
> Assignee: DIPAYAN BHOWMICK
> Fix For: 2.2.0
>
> Attachments: AMBARI-14228_branch-2.1.patch
>
>
> PROBLEM: In the files view Ambari only seems to be looking at user, group,
> mode which comes back from a GETSTATUS call and making the access decision
> based on that in the client.
> Doing it this way completely ignores alternate authorization mechanisms like
> HDFS ACLs and Ranger. Particularly with HDFS' new pluggable interface for
> authorization in Hadoop 2.7 this problem could get worse down the road.
> Ambari needs to deal with this in a uniform way so the user gets all of the
> access coming to them.
> BUSINESS IMPACT: Ambari files view is potentially useless to customers who
> have built an authorization model on anything other than user/group/mode,
> such as Ranger or HDFS ACLs
> EXPECTED RESULTS: The user should see no difference in their privilege level
> between Ambari Files View and FSShell.
> ACTUAL RESULTS: Only user/group/mode are considered in files view
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
