Details
-
Sub-task
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
2.1.0-beta, 3.0.0-alpha1
-
None
-
Incompatible change, Reviewed
-
The RPC client now waits for the Server's SASL negotiate response before instantiating its SASL client.
Description
As of HADOOP-9421, a RPCv9 server will advertise its authentication methods. This is meant to support features such as IP failover, better token selection, and interoperability in a heterogenous security environment.
Currently the client ignores the negotiate response and just blindly attempts to authenticate instead of choosing a mutually agreeable auth method.