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 3CE5FDC6A for ; Wed, 13 Mar 2013 07:20:17 +0000 (UTC) Received: (qmail 44152 invoked by uid 500); 13 Mar 2013 07:20:16 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 44083 invoked by uid 500); 13 Mar 2013 07:20:16 -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 44054 invoked by uid 99); 13 Mar 2013 07:20:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Mar 2013 07:20:15 +0000 Date: Wed, 13 Mar 2013 07:20:15 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-7101) UserGroupInformation.getCurrentUser() fails when called from non-Hadoop JAAS context 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-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600908#comment-13600908 ] Suresh Srinivas commented on HADOOP-7101: ----------------------------------------- bq. Let's continue the discussion there, instead of on this CLOSED issue. Sure. Generally if the port is straightforward, this issue could also be opened to attach the branch-1 patch. > UserGroupInformation.getCurrentUser() fails when called from non-Hadoop JAAS context > ------------------------------------------------------------------------------------ > > Key: HADOOP-7101 > URL: https://issues.apache.org/jira/browse/HADOOP-7101 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 0.22.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Blocker > Fix For: 0.22.0 > > Attachments: hadoop-7101.txt > > > If a Hadoop client is run from inside a container like Tomcat, and the current AccessControlContext has a Subject associated with it that is not created by Hadoop, then UserGroupInformation.getCurrentUser() will throw NoSuchElementException, since it assumes that any Subject will have a hadoop User principal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira