Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 26 Nov 2015 06:09:11 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12903557.1444345609000.200184.1448518151123@Atlassian.JIRA>
In-Reply-To: <JIRA.12903557.1444345609000@Atlassian.JIRA>
References: <JIRA.12903557.1444345609000@Atlassian.JIRA>
 <JIRA.12903557.1444345609999@arcas>
Subject: [jira] [Commented] (HADOOP-12468) Partial group resolution failure
 should not result in user lockout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-12468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028246#comment-15028246 ] 

Hudson commented on HADOOP-12468:
---------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #727 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/727/])
HADOOP-12468. Partial group resolution failure should not result in user (yzhang: rev 0348e769abc507c69d644db7bc56d31d971c51d1)
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/ShellBasedUnixGroupsMapping.java
* hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestShellBasedUnixGroupsMapping.java
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
* hadoop-common-project/hadoop-common/CHANGES.txt


> Partial group resolution failure should not result in user lockout
> ------------------------------------------------------------------
>
>                 Key: HADOOP-12468
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12468
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.1
>         Environment: Linux
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Minor
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-12468.001.patch, HADOOP-12468.002.patch, HADOOP-12468.003.patch, HADOOP-12468.004.patch, HADOOP-12468.005.patch, HADOOP-12468.006.patch, HADOOP-12468.007.patch, HADOOP-12468.008.patch, HADOOP-12468.009.patch, HADOOP-12468.010.patch
>
>
> If a Hadoop cluster is configured to use ShellBasedUnixGroupsMapping for user/group name mapping, occasionally some group names may become unresolvable (for example, using SSSD). 
> ShellBasedUnixGroupsMapping uses shell command "id -Gn" to retrieve the group name of a user; however, the existing logic assumes that if the exit code of the command is non-zero, the user has no group name at all. The shell command in Linux returns non-zero exit code if a group name is not resolvable. Unfortunately, it is possible that a user belongs to multiple groups, and any partial failure in group name resolution would denied the user's access.
> On the other hand, the JNI implementation (JniBasedUnixGroupsMapping) is more resilient. If any group name is unresolvable, it is simply ignored, and whatever are resolvable are returned.
> It is arguable that if the group name is not resolvable, the administrator should configure their directory/authentication service correctly, and Hadoop is in no position to handle it, but since the existing unit tests assume the output of JNI-based and shell-based implementation are the same, we should improve the shell-based group name resolution, and make it as resilient as the JNI-based one.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)