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 25911119A7 for ; Sat, 30 Aug 2014 05:57:54 +0000 (UTC) Received: (qmail 97155 invoked by uid 500); 30 Aug 2014 05:57:53 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 97015 invoked by uid 500); 30 Aug 2014 05:57:53 -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 96904 invoked by uid 99); 30 Aug 2014 05:57:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Aug 2014 05:57:53 +0000 Date: Sat, 30 Aug 2014 05:57:53 +0000 (UTC) From: "Benoy Antony (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-10651) Add ability to restrict service access using IP addresses and hostnames 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-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-10651: ---------------------------------- Attachment: (was: HADOOP-10651.patch) > Add ability to restrict service access using IP addresses and hostnames > ----------------------------------------------------------------------- > > Key: HADOOP-10651 > URL: https://issues.apache.org/jira/browse/HADOOP-10651 > Project: Hadoop Common > Issue Type: Sub-task > Components: security > Affects Versions: 2.5.0 > Reporter: Benoy Antony > Assignee: Benoy Antony > Attachments: HADOOP-10651.patch, HADOOP-10651.patch > > > In some use cases, it make sense to authorize the usage of some services only from specific hosts. Just like ACLS for Service Authorization , there can be a list of hosts for each service and this list can be checked during authorization. > Similar to ACLS, there can be a whitelist of ip and blacklist of ips. The default whitelist will be * and default blacklist will be empty. It should be possible to override the default whitelist and default blacklist. It should be possible to define whitelist and blacklist per service. > It should be possible to define ip ranges in blacklists and whitelists -- This message was sent by Atlassian JIRA (v6.2#6252)