Kumar
Kumar

Reputation: 4010

HBase error disabled security features are not available

Configured secure HBase-1.1.2 with Hadoop-2.7.1 on Windows. When i enable authorization referring Configuring HBase Authorization, getting ERROR: DISABLED: Security features are not available exception.

I have set the authorization configurations as below,

Configuration

<property>
     <name>hbase.security.authorization</name>
     <value>true</value>
</property>

<property>
     <name>hbase.coprocessor.master.classes</name>
     <value>org.apache.hadoop.hbase.security.access.AccessController</value>
</property>

<property>
     <name>hbase.coprocessor.region.classes</name> 
     <value>org.apache.hadoop.hbase.security.token.TokenProvider,org.apache.hadoop.hbase.security.access.AccessController</value>
</property>

enter image description here

But HBase Authorization works fine when i tried with HBase-0.98.13 version. Some one help me to enable HBase Authorization in a correct way.

Upvotes: 1

Views: 3660

Answers (2)

amazingW
amazingW

Reputation: 1

I was encountered with the same problem as I was not able to grant privileges to any other users. Mine was Kerberized Hadoop cluster.In addition to,My zookeeper was kerberized.So I do the following things: firstly,you need stop your hbase. Add the following to {$ZOOKEEPER_CONF_DIR}/jaas.conf:

Client{
    com.sun.security.auth.module.Krb5LoginModule required
    useKeyTab=true
    keyTab="/var/local/hadoop/zookeeper-3.4.8/conf/keytabs/hbase.keytab"
    storeKey=true
    useTicketCache=true
    principal="hbase/[email protected]";
};

(My hbase principal is:hbase/[email protected],username must be same)

then,use zkCli.sh command Line,next you can use: rmr /hbase to rmove the hbase directory,then start your hbase service,you will solve this problem.

Upvotes: 0

AKs
AKs

Reputation: 1745

I was encountered with the same problem as I was not able to grant privileges to any other users. Mine was Kerberized Hadoop cluster I did following changes to make it work.

hbase.security.authentication=kerberos
hbase.security.authorization=true

Then re-deployed the configurations then it worked fine.

Upvotes: 1

Related Questions