[
https://issues.apache.org/jira/browse/HBASE-14426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496877#comment-16496877
]
Josh Elser commented on HBASE-14426:
------------------------------------
{quote}Yes, at application level our client has defined their own customized
auth provider with a different scheme.
{quote}
Cool. Does the HBase login to obtain credentials to talk to ZooKeeper still
occur via JAAS?
> 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)
