You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2013/10/22 20:36:45 UTC

[jira] [Updated] (ZOOKEEPER-1554) Can't use zookeeper client without SASL

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

Patrick Hunt updated ZOOKEEPER-1554:
------------------------------------

    Fix Version/s: 3.5.0
                   3.4.6

This seems serious (currently listed as a blocker). Do we need to address this for 3.4.6? Any insight into whether this is addressed as noted in earlier comments on this jira? Are we sure this is addressed in 3.5.0?

> Can't use zookeeper client without SASL
> ---------------------------------------
>
>                 Key: ZOOKEEPER-1554
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1554
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.4.4
>            Reporter: Guillaume Nodet
>            Priority: Blocker
>             Fix For: 3.4.6, 3.5.0
>
>
> The ZooKeeperSaslClient correctly detects that it should not use SASL when nothing is configured, however the SendThread waits forever because clientTunneledAuthenticationInProgress() returns true instead of false.



--
This message was sent by Atlassian JIRA
(v6.1#6144)