[
https://issues.apache.org/jira/browse/HADOOP-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoy Antony updated HADOOP-10211:
----------------------------------
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.
was:
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.
> Enable RPC protocol to negotiate SASL-QOP values between client and servers
> ---------------------------------------------------------------------------
>
> Key: HADOOP-10211
> URL: https://issues.apache.org/jira/browse/HADOOP-10211
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.2.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
