You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Yuliya Feldman (JIRA)" <ji...@apache.org> on 2016/01/13 22:33:39 UTC
[jira] [Commented] (ZOOKEEPER-2159) Pluggable SASL Authentication
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097036#comment-15097036 ]
Yuliya Feldman commented on ZOOKEEPER-2159:
-------------------------------------------
[[~fpj] Would you have time now to review? - since 3.4.7 came and gone
> Pluggable SASL Authentication
> -----------------------------
>
> Key: ZOOKEEPER-2159
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2159
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client, server
> Reporter: Yuliya Feldman
> Assignee: Yuliya Feldman
> Fix For: 3.5.2, 3.6.0
>
> Attachments: PluggableZookeeperAuthentication (1).pdf, PluggableZookeeperAuthentication.pdf
>
>
> Today SASLAuthenticationProvider is used for all SASL based authentications which creates some "if/else" statements in ZookeeperSaslClient and ZookeeperSaslServer code with just Kerberos and Digest.
> We want to use yet another different SASL based authentication and adding one more "if/else" with some code specific just to that new way does not make much sense.
> Proposal is to allow to plug custom SASL Authentication mechanism(s) without further changes in Zookeeper code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)