HBase access control features are in active development at the moment. Currently we're building on top of secure Hadoop and using Kerberos for client authentication, with HBase providing additional tools for managing access to individual tables or column families. See the following issues in JIRA:
https://issues.apache.org/jira/browse/HBASE-1697 https://issues.apache.org/jira/browse/HBASE-3025 The current code is functional for basic read/write permissions, but is definitely a work in progress. If you'd like to track the progress, you can find it at: https://github.com/trendmicro/hbase/tree/security But the code base is in active development, changing frequently, and depends upon some features that are not yet present in HBase trunk. If you have specific needs for security, please comment on the JIRAs or start checking out the code. Additional thoughts or contributions are definitely welcome! Regardless of any security layer within HBase, however, you'll still want to firewall off your cluster and limit access to only your clients at the iptables/netfilter level. Having a publicly exposed Hadoop/HBase cluster is not a good idea. Gary On Wed, Nov 3, 2010 at 6:30 AM, Sean Bigdatafun <[email protected]>wrote: > CDH3beta3 seems to provide what you want (ACL) > > > On Wed, Nov 3, 2010 at 1:56 AM, 梁景明 <[email protected]> wrote: > > > hi , is there any features for me to control the client to access to my > > hbase. > > like some authority ,some user or some password? > > > > now one way to control > > my servers use iptables to control the access, is there any better way ? > > thanks. > > > > > > -- > --Sean >
