Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 793DF1183D for ; Wed, 2 Jul 2014 00:21:31 +0000 (UTC) Received: (qmail 188 invoked by uid 500); 2 Jul 2014 00:21:31 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 99969 invoked by uid 500); 2 Jul 2014 00:21:31 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 99946 invoked by uid 99); 2 Jul 2014 00:21:31 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2014 00:21:31 +0000 Date: Wed, 2 Jul 2014 00:21:31 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11344) Hide row keys and such from the web UIs 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/HBASE-11344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049455#comment-14049455 ] stack commented on HBASE-11344: ------------------------------- Why not just put these utility methods into HRI? A dedicated class at the top level strikes me as assigning this little little facility more import than it warrants. Otherwise looks good. Needs release note. > Hide row keys and such from the web UIs > --------------------------------------- > > Key: HBASE-11344 > URL: https://issues.apache.org/jira/browse/HBASE-11344 > Project: HBase > Issue Type: Improvement > Reporter: Devaraj Das > Assignee: Devaraj Das > Fix For: 0.99.0 > > Attachments: 11344-1.txt, 11344-2.txt > > > The table details on the master UI lists the start row keys of the regions. The row keys might have sensitive data. We should hide them based on whether or not the user accessing has the required authorization to view the table.. To start with, we could make the display of row keys and such based on a configuration being true or false. If it is false, such potentially sensitive data is never displayed on the web UI. -- This message was sent by Atlassian JIRA (v6.2#6252)