[
https://issues.apache.org/jira/browse/HADOOP-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-10221:
---------------------------------
Attachment: HADOOP-10221.no-static.example
Sorry this jira's review has been delayed, I was dealing with internal issues.
Here's an example patch of what I meant in my original review about removing
the static nature of qop. Currently its a global configuration whereby
multiple rpc instances can stomp on each others configuration.
This is a completely uncompiled & untested example patch. Hopefully we can
kill two birds with one stone: sasl property configuration is pluggable, and
rpc servers may each manage their own sasl properties. Oh, and I added your
resolver concept to the rpc client too.
> 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.no-static.example, HADOOP-10221.patch,
> HADOOP-10221.patch, HADOOP-10221.patch, HADOOP-10221.patch,
> HADOOP-10221.patch, 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.2#6252)
