[
https://issues.apache.org/jira/browse/HADOOP-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902129#comment-13902129
]
Daryn Sharp commented on HADOOP-10221:
--------------------------------------
Still pondering, but {{Connection#attemptingUser}} is not defined until after
SASL negotiation is in progress. I'm not sure why it's being passed to the
resolver that will be used to create the SASL object because won't it always be
null?
> 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, 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)
