You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/09/09 05:47:33 UTC

[jira] Created: (HADOOP-6946) SecurityUtils' TGT fetching does not fall back to "login" user

SecurityUtils' TGT fetching does not fall back to "login" user
--------------------------------------------------------------

                 Key: HADOOP-6946
                 URL: https://issues.apache.org/jira/browse/HADOOP-6946
             Project: Hadoop Common
          Issue Type: Bug
          Components: security
    Affects Versions: 0.22.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


In SecurityUtil.getTgtFromSubject and SecurityUtil.fetchServiceTicket, the current JAAS Subject is fetched directly from the AccessController, rather than using UserGroupInformation.getCurrentUser().getSubject(). This means that if it is not run in the confines of a doAs() block, it will fail since the current JAAS subject is null, even though SecurityUtil.login(...) may have been called.

In practice, one place this shows up is using the secondary namenode's "-checkpoint force" option in secured 0.20, since it's done inside the main thread with no surrounding doAs().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.