From common-issues-return-162524-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Dec 21 18:23:48 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2345A180627 for ; Fri, 21 Dec 2018 18:23:47 +0100 (CET) Received: (qmail 18738 invoked by uid 500); 21 Dec 2018 17:23:47 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 18725 invoked by uid 99); 21 Dec 2018 17:23:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2018 17:23:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 881D3C77D7 for ; Fri, 21 Dec 2018 17:23:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Kxg4WmbQWygE for ; Fri, 21 Dec 2018 17:23:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2591E5F532 for ; Fri, 21 Dec 2018 17:16:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AC794E092E for ; Fri, 21 Dec 2018 17:16:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 673672401A for ; Fri, 21 Dec 2018 17:16:00 +0000 (UTC) Date: Fri, 21 Dec 2018 17:16:00 +0000 (UTC) From: "Bolke de Bruin (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HADOOP-15996) Plugin interface to support more complex usernames in Hadoop MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-15996?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 726902#comment-16726902 ]=20 Bolke de Bruin edited comment on HADOOP-15996 at 12/21/18 5:15 PM: ------------------------------------------------------------------- 0002 patch version cleans up the code a little bit and adds / fixes documen= tation =C2=A0 [~eyang] I'm still a bit puzzled why it is not picked up in your config. Te= sts do cover the 'mapping' (see TestUsergroupInformation). Did you recompil= e hadoop-common as well? Setting the mapping happens in HadoopKerberosName = as happens with NAME_RULES. =C2=A0 [~lmccay] Documentation corrected and updated. PTAL. was (Author: bolke): 0002 patch version cleans up the code a little bit and adds / fixes documen= tation =C2=A0 [~eyang] I'm still a bit puzzled why it is not picked up in your config. Te= sts do cover the 'mapping' (see TestUsergroupInformation). Did you recompil= e hadoop-common as well? Setting the mapping happens in HadoopKerberosName = as happens with NAME_RULES. > Plugin interface to support more complex usernames in Hadoop > ------------------------------------------------------------ > > Key: HADOOP-15996 > URL: https://issues.apache.org/jira/browse/HADOOP-15996 > Project: Hadoop Common > Issue Type: New Feature > Components: security > Reporter: Eric Yang > Assignee: Bolke de Bruin > Priority: Major > Attachments: 0001-HADOOP-15996-Make-auth-to-local-configurable.pa= tch, 0001-Simple-trial-of-using-krb5.conf-for-auth_to_local-ru.patch, 0002-= HADOOP-15996-Make-auth-to-local-configurable.patch > > > Hadoop does not allow support of @ character in username in recent securi= ty mailing list vote to revert HADOOP-12751.=C2=A0 Hadoop auth_to_local rul= e must match to authorize user to login to Hadoop cluster.=C2=A0 This desig= n does not work well in multi-realm environment where identical username be= tween two realms=C2=A0do not map to the same user.=C2=A0 There is also poss= ibility that lossy regex can incorrectly map users.=C2=A0 In the interest o= f supporting multi-realms, it maybe preferred to pass principal name withou= t rewrite to uniquely=C2=A0distinguish users.=C2=A0 This=C2=A0jira is to re= visit if Hadoop can support full principal names without rewrite and=C2=A0p= rovide a plugin to=C2=A0override Hadoop's default implementation of auth_to= _local for multi-realm use case. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org