[
https://issues.apache.org/jira/browse/HADOOP-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598632#comment-13598632
]
Torsten Mielke commented on HADOOP-7101:
----------------------------------------
Filling in for Claus Ibsen here as well:
{quote}Can you tell me the branch name and commit revision for this?{quote}
The latest 0.23.5 release has this fix included.
However we did not find any 1.x release that contains this code fix. See my
comment from 01/Feb/13.
I checked the source code of all relevant 1.x releases and did not see the fix.
The fix is present in 2.0 branch however there has not been any release of 2.0
yet.
So trying to use the Hadoop client libs of any 1.x version when running inside
another container (e.g. OSGi) fails.
> 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
