[
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated ZOOKEEPER-1437:
-------------------------------------
Attachment: ZOOKEEPER-1437.patch
ZOOKEEPER-1437.patch
This patch adds an authSync object to ClientCnxn. If client is configured for
SASL authentication, client's main thread will wait() on authSync. SendThread
will authSync() when SASL negotiation with Zookeeper server is complete
(whether successfully or not).
I removed the sleep()s from SaslAuthTest and other Sasl tests which were hiding
this issue : now the clients immediately attempt to create zk nodes, as with to
Thomas's test case of running zkCli with an immediate get.
However, because of removing the sleep()s that hid the issue, the test
SaslAuthMissingClientConfigTest hangs. This is because the zooKeeperSaslClient
is null because SASL configuration is intentionally bad and the SASL setup has
therefore failed. This failure mode needs to be distinguished from the case
where zooKeeperSaslClient is null because it hasn't been constructed yet. This
remains to be done, so not marking this issue as "Patch Available" yet.
> Client uses session before SASL authentication complete
> -------------------------------------------------------
>
> Key: ZOOKEEPER-1437
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1437
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.3
> Reporter: Thomas Weise
> Assignee: Eugene Koontz
> Attachments: ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch
>
>
> Found issue in the context of hbase region server startup, but can be
> reproduced w/ zkCli alone.
> getData may occur prior to SaslAuthenticated and fail with NoAuth. This is
> not expected behavior when the client is configured to use SASL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
