Josh Elser 78eecd3a7d HBASE-23381 Ensure Netty client receives at least one response before considering SASL negotiation complete ... The PLAIN mechanism test added in the Shade authentication example has different semantics than GSSAPI mechanism -- the client reports that the handshake is done after the original challenge is computed. The javadoc on SaslClient, however, tells us that we need to wait for a response from the server before proceeding. The client, best as I can see, does not receive any data from HBase; however the application semantics (e.g. throw an exception on auth'n error) do not work as we intend as a result of this bug. Extra trace logging was also added to debug this, should a similar error ever happen again with some other mechanism. Closes #1260 Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bharath Vissapragada <bharathv@apache.org>		2020-03-26 18:34:47 -04:00
..
src	HBASE-23381 Ensure Netty client receives at least one response before considering SASL negotiation complete	2020-03-26 18:34:47 -04:00
pom.xml	HBASE-23077 move entirely to spotbugs (#1265)	2020-03-12 10:18:09 +08:00