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 2015/05/01 20:38:06 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=14523624#comment-14523624 ] 

Yuliya Feldman commented on ZOOKEEPER-2159:
-------------------------------------------

[~ekoontz] I have updated reviewboard and replied to all the comments you have made. Did you have a chance to test Kerberos and do you mind give another pass on review request.
Thanks.

> 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
>         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)