[
https://issues.apache.org/jira/browse/HADOOP-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601051#comment-13601051
]
Matthew Farrellee commented on HADOOP-7101:
-------------------------------------------
[~sureshms]
Re CLOSED - ok, my background w/ workflows is that once CLOSED leave closed,
open a new issue
Re version - I've only been able to find the fix for HADOOP-7101 on the 0.23.*
and 2.0.* release tags. That may mean this issue was not actually fixed in
0.22.0. However, I'm not familiar enough with the version streams to say for
sure.
> 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.branch-1.patch, 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
