Description
SASL allows different types of protection are referred to as the quality of protection (qop). It is negotiated between the client and server during the authentication phase of the SASL exchange. Currently hadoop allows specifying a single QOP value via hadoop.rpc.protection.
The enhancement enables a user to specify multiple QOP values - authentication, integrity, privacy as a comma separated list via hadoop.rpc.protection
The client and server can have different set of values for hadoop.rpc.protection and they will negotiate to determine the QOP to be used for communication.
Attachments
Attachments
Issue Links
- breaks
-
HADOOP-10391 HADOOP-10211 change for comma-separated list of QOP values broke backwards-compatibility with existing configs.
- Resolved
-
SPARK-5111 HiveContext and Thriftserver cannot work in secure cluster beyond hadoop2.5
- Resolved
-
HIVE-6987 Metastore qop settings won't work with Hadoop-2.4
- Closed
- is depended upon by
-
HADOOP-10221 Add a plugin to specify SaslProperties for RPC protocol based on connection properties
- Closed
- is related to
-
HADOOP-10057 Add ability in Hadoop servers (Namenode, JobTracker, Datanode ) to support multiple QOP (Authentication , Privacy) simultaneously
- Resolved