zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2159) Pluggable SASL Authentication
Date Wed, 23 Nov 2016 20:01:59 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691238#comment-15691238
] 

Michael Han commented on ZOOKEEPER-2159:
----------------------------------------

bq. (not sure if by mistake or not).

Yeah, it is not obvious to me why this issue was marked as a Blocker. 
cc [~phunt].

> 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.3, 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)

Mime
View raw message