Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0520DB2C for ; Mon, 11 Feb 2013 13:08:18 +0000 (UTC) Received: (qmail 59538 invoked by uid 500); 11 Feb 2013 13:08:16 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 59368 invoked by uid 500); 11 Feb 2013 13:08:15 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 59334 invoked by uid 99); 11 Feb 2013 13:08:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 13:08:14 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rmorgan466@gmail.com designates 209.85.219.50 as permitted sender) Received: from [209.85.219.50] (HELO mail-oa0-f50.google.com) (209.85.219.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 13:08:08 +0000 Received: by mail-oa0-f50.google.com with SMTP id l20so6250308oag.9 for ; Mon, 11 Feb 2013 05:07:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=7UjDeKJvp2BlHMxmnqKf4IbgV7b4TD9wImhDWcGK7Xw=; b=OHJuIcYAx/lt21YlzCOEyrRGY//BYqYjbetBeI5JDMMhGb7MWgo78DjEFe/4SntMfq AZrxoIZCc6gxXtJ2+7IeJAG8X5VV2RxVNGJ9RWXt/KdoQuawtEY0+vDMWj9m+l+Mux5Q Ik2V+7puIKX1f+vqnN4GgDH1vkJwtp1ZoX1HozxfIlWr18yiKCsWTdm6VLdN9Y0ISm9j EPBCMkwIVYnCiHTy8+SolPM6Apsh6xjvET8PrjnhB6K7fwgZTiNjLoYdV1ZlkwHXaI/N ejsSBd/in+qYxahAi/O+mZA8a0WDzDcy396ZiXaaCxzN2rg0uRqDFQV3gonHRAQTr+o4 s8CA== MIME-Version: 1.0 X-Received: by 10.60.1.129 with SMTP id 1mr10341832oem.93.1360588067160; Mon, 11 Feb 2013 05:07:47 -0800 (PST) Received: by 10.76.170.200 with HTTP; Mon, 11 Feb 2013 05:07:46 -0800 (PST) In-Reply-To: References: Date: Mon, 11 Feb 2013 08:07:46 -0500 Message-ID: Subject: Re: restrict clients From: Rita To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8fb1f4f46dc3ce04d572980b X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb1f4f46dc3ce04d572980b Content-Type: text/plain; charset=ISO-8859-1 Hi, I am looking for more than an ACL. I want to control what clients can connect to the hbase cluster. Is that possible? On Fri, Feb 8, 2013 at 10:36 AM, Stas Maksimov wrote: > Hi Rita, > > As far as I know ACL is on a user basis. Here's a link for you: > http://hbase.apache.org/book/hbase.accesscontrol.configuration.html > > Thanks, > Stas > > > On 8 February 2013 15:20, Rita wrote: > > > Hi, > > > > In an enterprise deployment, how can I restrict who can access the data? > > For example, I want only certain servers able to GET,PUT data everyone > else > > should be denied. Is this possible? > > > > > > > > -- > > --- Get your facts first, then you can distort them as you please.-- > > > -- --- Get your facts first, then you can distort them as you please.-- --e89a8fb1f4f46dc3ce04d572980b--