hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7101) UserGroupInformation.getCurrentUser() fails when called from non-Hadoop JAAS context
Date Fri, 14 Jan 2011 07:13:46 GMT

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

Todd Lipcon commented on HADOOP-7101:
-------------------------------------

Yes, I agree the whole concept of loginUser fallback feels wrong... but like you said, outside
the scope of this patch.

To add a datapoint about testing - the user who was experiencing this issue inside tomcat
tested the patch and reports the problem is indeed fixed.

I'll commit to 0.22 and trunk shortly.

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message