[
https://issues.apache.org/jira/browse/ZOOKEEPER-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653431#comment-13653431
]
jorge allen commented on ZOOKEEPER-1554:
----------------------------------------
I worked around a quick fix until the next release. If you are not using sasl.
You can make it believe it has sasl authentication, but give it a bogus path:
System.setProperty("java.security.auth.login.config","/boguspath/at/home");
This will cause it to go into the method, but once it tries to open the
authentication file, it will throw the SecurityException which will cause the
code to return false when it catches it.
Jorge Allen
[email protected]
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
