[HBASE-24579] Failed SASL authentication does not result in an exception on client side

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.2.5
• Fix Version/s: 3.0.0-alpha-1, 2.3.0, 2.2.6
• Component/s: rpc
• Assignee: Szabolcs Bukros
• Reporter: Szabolcs Bukros
• Created: 17/Jun/20 09:30
• Updated: 14/Jul/22 13:43
• Resolved: 23/Jun/20 09:05

Description

When HBaseSaslRpcClient.saslConnect tries to authenticate it only reads the input stream if the process is not complete yet. However if the authentication failed and the process is completed the exception sent back in the stream never gets read.

We should always try to read the input stream even if the process is complete to make sure it was empty.

Issue Links

• breaks: HBASE-27204 BlockingRpcClient will hang for 20 seconds when SASL is enabled after finishing negotiation
• links to: GitHub Pull Request #1921
• links to: GitHub Pull Request #1951