Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CA3E310CA2 for ; Thu, 6 Mar 2014 22:51:47 +0000 (UTC) Received: (qmail 35670 invoked by uid 500); 6 Mar 2014 22:51:46 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 35597 invoked by uid 500); 6 Mar 2014 22:51:46 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 35586 invoked by uid 99); 6 Mar 2014 22:51:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 22:51:45 +0000 Date: Thu, 6 Mar 2014 22:51:45 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-10221) Add a plugin to specify SaslProperties for RPC protocol based on connection properties MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)