[
https://issues.apache.org/jira/browse/HBASE-14426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496664#comment-16496664
]
Josh Elser commented on HBASE-14426:
------------------------------------
{quote}This configuration will be useful in case where user has configured a
customized auth provider in ZK instead of default one, they can have a
different auth scheme for that.
{quote}
Thanks, that makes sense, Pankaj.
I think that would boil down to whether or not we want to support this via
HBase. Is this a compelling use-case for us to take the burden in supporting? I
would be worried about creating this customization but then forgetting that we
did and breaking it again. Do you have a custom ZK auth provider implemented
that you're trying to support (or are you just being helpful)?
> 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)
