[
https://issues.apache.org/jira/browse/HADOOP-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116265#comment-14116265
]
Hadoop QA commented on HADOOP-10651:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12665544/HADOOP-10651.patch
against trunk revision 270a271.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4603//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4603//console
This message is automatically generated.
> 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)
