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

Tamas Penzes updated ZOOKEEPER-2159:
------------------------------------
    Priority: Major  (was: Blocker)

> 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: Major
>             Fix For: 3.6.0, 3.5.5
>
>         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
(v7.6.3#76005)

Reply via email to