You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Pankaj Kumar (JIRA)" <ji...@apache.org> on 2018/07/24 14:22:00 UTC
[jira] [Commented] (HBASE-14426) Authentication provider is hard
coded as "sasl"
[ https://issues.apache.org/jira/browse/HBASE-14426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554292#comment-16554292 ]
Pankaj Kumar commented on HBASE-14426:
--------------------------------------
[~elserj] Please provide your opinion.
> 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)