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/06 21:45:33 UTC

[jira] [Commented] (ZOOKEEPER-2314) Improvements to SASL

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

Michael Han commented on ZOOKEEPER-2314:
----------------------------------------

Update priority - I don't think this is a blocker; as previously mentioned, this is an umbrella JIRA with two sub-tasks; one task is resolved and the other task is not a blocker priority task. 

> Improvements to SASL
> --------------------
>
>                 Key: ZOOKEEPER-2314
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 3.4.6, 3.5.1
>            Reporter: Flavio Junqueira
>            Assignee: Flavio Junqueira
>             Fix For: 3.5.3, 3.6.0, 3.4.11
>
>
> Points that occur to me right now:
> # The login object in ZooKeeperSaslClient is static, which means that if you try to create another client for tests, the login object will be the first one you've set for all runs. I've experienced this with 3.4.6.
> # There are a number of properties spread across the code that do not appear in the docs. For example, zookeeper.allowSaslFailedClients isn't documented afaict.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)