You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:08 UTC

[jira] [Updated] (ZOOKEEPER-2159) Pluggable SASL Authentication

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han updated ZOOKEEPER-2159:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> 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
>            Priority: Blocker
>             Fix For: 3.5.4, 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.15#6346)