Return-Path: 
 <issues-return-8028-apmail-ambari-issues-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org
Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5908919FC8
	for <apmail-ambari-issues-archive@minotaur.apache.org>;
 Fri, 29 Apr 2016 07:47:13 +0000 (UTC)
Received: (qmail 73926 invoked by uid 500); 29 Apr 2016 07:47:13 -0000
Delivered-To: apmail-ambari-issues-archive@ambari.apache.org
Received: (qmail 73908 invoked by uid 500); 29 Apr 2016 07:47:13 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 73888 invoked by uid 99); 29 Apr 2016 07:47:12 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2016 07:47:12 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id CF8012C0451
	for <issues@ambari.apache.org>; Fri, 29 Apr 2016 07:47:12 +0000 (UTC)
Date: Fri, 29 Apr 2016 07:47:12 +0000 (UTC)
From: "DIPAYAN BHOWMICK (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12963774.1461913416000.68137.1461916032846@Atlassian.JIRA>
In-Reply-To: <JIRA.12963774.1461913416000@Atlassian.JIRA>
References: <JIRA.12963774.1461913416000@Atlassian.JIRA>
 <JIRA.12963774.1461913416360@arcas>
Subject: [jira] [Updated] (AMBARI-16177) Views: User should be able to
 assign permission of a view instance to cluster roles
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

DIPAYAN BHOWMICK updated AMBARI-16177:
--------------------------------------
    Status: Patch Available  (was: Open)

> Views: User should be able to assign permission of a view instance to cluster roles 
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16177
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16177
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.2.0
>            Reporter: DIPAYAN BHOWMICK
>            Assignee: DIPAYAN BHOWMICK
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16177.trunk.patch
>
>
> Currently, "USE" permission for users + groups needs to manually mapped by an Ambari Admin for each view instance.
> In cases where a view can be auto-configured for a locally managed cluster and we expect that view to be available to that same users that have Cluster Operator or other role access to that cluster, we need to provide an option for Ambari Admins to inherit USE permission on view instances from the cluster permissions. This means:
> - Any user or group with different role on the cluster will also get USE access on the view instance.
> - This should be available in-addition-to specific view USE permission mapping
> - This should be available from Ambari Administration interface and optional set during <auto-create>
> - Views like Capacity Scheduler and Tez UI should be adjusted to use this feature for their auto-create instances



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