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 61F8394DB for ; Fri, 25 May 2012 18:46:24 +0000 (UTC) Received: (qmail 65155 invoked by uid 500); 25 May 2012 18:46:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 65063 invoked by uid 500); 25 May 2012 18:46:23 -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 64834 invoked by uid 99); 25 May 2012 18:46:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2012 18:46:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 9FF1E142826 for ; Fri, 25 May 2012 18:46:23 +0000 (UTC) Date: Fri, 25 May 2012 18:46:23 +0000 (UTC) From: "Matteo Bertozzi (JIRA)" To: issues@hbase.apache.org Message-ID: <1003996683.3480.1337971583658.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1541800002.10532.1337747200947.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (HBASE-6068) Secure HBase cluster : Client not able to call some admin APIs 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-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi updated HBASE-6068: ----------------------------------- Attachment: HBASE-6068-v1.patch Missed one in the list, hbase shell call Zookeeper directly on zk_dump command zk_dump -> listChildrenNoWatch() /hbase/backup-masters/* > Secure HBase cluster : Client not able to call some admin APIs > -------------------------------------------------------------- > > Key: HBASE-6068 > URL: https://issues.apache.org/jira/browse/HBASE-6068 > Project: HBase > Issue Type: Bug > Components: security > Affects Versions: 0.92.1, 0.94.0, 0.96.0 > Reporter: Anoop Sam John > Assignee: Matteo Bertozzi > Attachments: HBASE-6068-v0.patch, HBASE-6068-v1.patch > > > In case of secure cluster, we allow the HBase clients to read the zk nodes by providing the global read permissions to all for certain nodes. These nodes are the master address znode, root server znode and the clusterId znode. In ZKUtil.createACL() , we can see these node names are specially handled. > But there are some other client side admin APIs which makes a read call into the zookeeper from the client. This include the isTableEnabled() call (May be some other. I have seen this). Here the client directly reads a node in the zookeeper ( node created for this table ) and the data is matched to know whether this is enabled or not. > Now in secure cluster case any client can read zookeeper nodes which it needs for its normal operation like the master address and root server address. But what if the client calls this API? [isTableEnaled () ]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira