[
https://issues.apache.org/jira/browse/HBASE-14426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496649#comment-16496649
]
Josh Elser commented on HBASE-14426:
------------------------------------
{quote}Better we have a configuration for this like
"hbase.zookeeper.authProvider.scheme" with "sasl" default value.
{quote}
[~pankaj2461], I'm not seeing the problem you're trying to solve. What does
having a configuration property to control the scheme allow an admin to do that
is supported by us? (I don't know of a reason why HBase would want to support
something other than SASL auth to ZK given the other deployment requirements we
have already). Thanks in advance..
> Authentication provider is hard coded as "sasl"
> -----------------------------------------------
>
> Key: HBASE-14426
> URL: https://issues.apache.org/jira/browse/HBASE-14426
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
> Reporter: Pankaj Kumar
> Assignee: Pankaj Kumar
> Priority: Major
>
> In ZKUtil.createACL(ZooKeeperWatcher zkw, String node, boolean
> isSecureZooKeeper),
> {code:java}
> if(!user.equals(hbaseUser)) {
> acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
> }
> {code}
> Here scheme is presently hard coded as "sasl", actually it should be based on
> the auth provider configured at ZK.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
