[ZOOKEEPER-1437] Client uses session before SASL authentication complete

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.3
• Fix Version/s: 3.4.4, 3.5.0
• Component/s: java client
• Hadoop Flags: Reviewed
• Assignee: Eugene Joseph Koontz
• Reporter: Thomas Weise
• Created: 29/Mar/12 02:09
• Updated: 18/Feb/16 12:31
• Resolved: 09/Sep/12 18:24

Description

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.

Issue Links

• breaks: ZOOKEEPER-1764 ZooKeeper attempts at SASL eventhough it shouldn't
• is related to: ZOOKEEPER-1455 there is no way to determine if a session is sasl authenticated or not
• is related to: ZOOKEEPER-1561 Zookeeper client may hang on a server restart
• is related to: HBASE-5780 Fix race in HBase regionserver startup vs ZK SASL authentication
• is related to: HBASE-7771 Secure HBase Client in MR job causes tasks to wait forever
• is related to: ZOOKEEPER-938 Support Kerberos authentication of clients.
• is related to: ZOOKEEPER-1547 Test robustness of client using SASL in the presence of dropped requests
• is related to: HADOOP-8315 Support SASL-authenticated ZooKeeper in ActiveStandbyElector