THRIFT-4506: fix use of assert for correctness in Java SASL negotiation

Client: java
This commit is contained in:
James E. King III 2018-03-05 11:34:21 -05:00
parent 9e0c927214
commit d973409661

View File

@ -287,7 +287,7 @@ abstract class TSaslTransport extends TTransport {
if (message.status == NegotiationStatus.COMPLETE && if (message.status == NegotiationStatus.COMPLETE &&
getRole() == SaslRole.CLIENT) { getRole() == SaslRole.CLIENT) {
LOGGER.debug("{}: All done!", getRole()); LOGGER.debug("{}: All done!", getRole());
break; continue;
} }
sendSaslMessage(sasl.isComplete() ? NegotiationStatus.COMPLETE : NegotiationStatus.OK, sendSaslMessage(sasl.isComplete() ? NegotiationStatus.COMPLETE : NegotiationStatus.OK,
@ -295,8 +295,6 @@ abstract class TSaslTransport extends TTransport {
} }
LOGGER.debug("{}: Main negotiation loop complete", getRole()); LOGGER.debug("{}: Main negotiation loop complete", getRole());
assert sasl.isComplete();
// If we're the client, and we're complete, but the server isn't // If we're the client, and we're complete, but the server isn't
// complete yet, we need to wait for its response. This will occur // complete yet, we need to wait for its response. This will occur
// with ANONYMOUS auth, for example, where we send an initial response // with ANONYMOUS auth, for example, where we send an initial response