Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 7 Nov 2016 19:27:59 +0000 (UTC)
From: "Lars George (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12949010.1457680719000.213162.1478546879353@Atlassian.JIRA>
In-Reply-To: <JIRA.12949010.1457680719000@Atlassian.JIRA>
References: <JIRA.12949010.1457680719000@Atlassian.JIRA> <JIRA.12949010.1457680719707@arcas>
Subject: [jira] [Assigned] (HBASE-15445) Add support for ACLs for web based
 UIs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 07 Nov 2016 19:28:06 -0000


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

Lars George reassigned HBASE-15445:
-----------------------------------

    Assignee: Lars George

> Add support for ACLs for web based UIs
> --------------------------------------
>
>                 Key: HBASE-15445
>                 URL: https://issues.apache.org/jira/browse/HBASE-15445
>             Project: HBase
>          Issue Type: Bug
>          Components: master, regionserver, REST, Thrift
>    Affects Versions: 1.2.0, 1.0.3, 1.1.3
>            Reporter: Lars George
>            Assignee: Lars George
>
> Since 0.99 and HBASE-10336 we have our own HttpServer class that (like the counterpart in Hadoop) supports setting an ACL to allow only named users to access the web based UIs of the server processes. In secure mode we should support this as it works hand-in-hand with Kerberos authorization and the UGI class. It seems all we have to do is add a property allowing to set the ACL property as a list of users and/or groups that have access to the UIs if needed.
> As an add-on, we could combine this with the {{read-only}} flag, so that some users can only access the UIs with any option to trigger, for example, splits. 


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