[
https://issues.apache.org/jira/browse/HBASE-13275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13275:
-----------------------------------
Fix Version/s: 0.98.13
1.1.0
1.0.1
2.0.0
Any thoughts on the compatibility ramifications. One can argue this is a bug,
we should have been respecting this setting. Can also argue changing this is a
functional change, if for some reason someone hasn't read the docs and whipped
up a config that installs the coprocessors but doesn't toggle
'hbase.security.authorization' on. Thoughts or concerns?
/cc [~enis] [~busbey] [~lhofhansl] [~stack]
> Setting hbase.security.authorization to false does not disable authorization
> when AccessController is in the coprocessor class list
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-13275
> URL: https://issues.apache.org/jira/browse/HBASE-13275
> Project: HBase
> Issue Type: Bug
> Reporter: William Watson
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.13
>
>
> According to the docs provided by Cloudera (we're not running Cloudera, BTW),
> this is the list of configs to enable authorization in HBase:
> {code}
> <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>
> {code}
> We wanted to then disable authorization but simply setting
> hbase.security.authorization to false did not disable the authorization
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
