hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7101) UserGroupInformation.getCurrentUser() fails when called from non-Hadoop JAAS context
Date Thu, 07 Feb 2013 07:45:16 GMT

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

Claus Ibsen commented on HADOOP-7101:
-------------------------------------

I mean when people uses Hadoop 0.2 and it works. Then if they upgrade to Hadoop 1.x and it
no longer works.
eg the fix only went into the 0.2 code branch, and not the 1.x code branch.
                
> 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

Mime
View raw message