[
https://issues.apache.org/jira/browse/HADOOP-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoy Antony updated HADOOP-10221:
----------------------------------
Attachment: HADOOP-10221.patch
Solution could be to allow SaslProperties (which includes QOP) to be decided
for each connection based on custom logic that can be plugged in.
SASLRPCServer obtains SASLProperties from a configured SASLPropertiesResolver
if one exists. If not , it falls backs to the default SASLProperites loaded
during initialization.
The feature is backward compatible.
Additional tests are enabled in TestSaslRPC
> Add a plugin to specify SaslProperties for RPC protocol based on connection
> properties
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-10221
> URL: https://issues.apache.org/jira/browse/HADOOP-10221
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.2.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HADOOP-10221.patch
>
>
> Add a plugin to specify SaslProperties for RPC protocol based on connection
> properties.
> HADOOP-10211 enables client and server to specify and support multiple QOP.
> Some connections needs to be restricted to a specific set of QOP based on
> connection properties.
> Eg. connections from client from a specific subnet needs to be encrypted
> (QOP=privacy)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
