Return-Path: 
 <dev-return-34190-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5305211EAA
	for <apmail-ambari-dev-archive@www.apache.org>;
 Wed, 30 Jul 2014 16:26:40 +0000 (UTC)
Received: (qmail 91284 invoked by uid 500); 30 Jul 2014 16:26:40 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 91185 invoked by uid 500); 30 Jul 2014 16:26:40 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 90925 invoked by uid 99); 30 Jul 2014 16:26:40 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jul 2014 16:26:40 +0000
Date: Wed, 30 Jul 2014 16:26:39 +0000 (UTC)
From: "Tom Beerbower (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12730825.1406737567978.76306.1406737599978@arcas>
In-Reply-To: <JIRA.12730825.1406737567978@arcas>
References: <JIRA.12730825.1406737567978@arcas>
Subject: [jira] [Created] (AMBARI-6679) Add Cluster Privilege Resource
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Tom Beerbower created AMBARI-6679:
-------------------------------------

             Summary: Add Cluster Privilege Resource
                 Key: AMBARI-6679
                 URL: https://issues.apache.org/jira/browse/AMBARI-6679
             Project: Ambari
          Issue Type: Task
            Reporter: Tom Beerbower
            Assignee: Tom Beerbower
             Fix For: 1.7.0


Add a cluster privilege resource provider so that privileges may be assigned to cluster instances.  See BUG-18967 for view instance privileges.
TODO :
#  Add resource_id column to clusters
#  Add resource entity relationship to ClusterEntity
#  Insert associated resource row in DB  when cluster is created.
#  Update existing cluster rows in DB with associated resource relationship.
#  Add cluster privilege service for API framework.
#  Add cluster privilege resource provider.
#  Adjust unit tests.

API:

To grant privileges to access the cluster we can create a privilege sub-resource for the cluster instance.  The following API will grant CLUSTER.READ permission to the user 'bob' for the cluster instance 'c1'.

{code}

    POST http://<server>/api/v1/clusters/c1
   
    [
      {
        "PrivilegeInfo" : {
          "permission_name" : "CLUSTER.READ",
          "principal_name" : "bob",
          "principal_type" : "USER"
        }
      }
    ]
{code}




--
This message was sent by Atlassian JIRA
(v6.2#6252)