hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sevada Abraamyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2892) Unable to get AMRMToken in unmanaged AM when using a secure cluster
Date Sat, 22 Nov 2014 17:46:13 GMT

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

Sevada Abraamyan commented on YARN-2892:
----------------------------------------

[~rohithsharma], I did intend to submit a patch. However, I couldn't find out how to assign
the issue to myself. Maybe I don't have the correct privaleges? In any case, if you have not
yet started on a patch, can you please assign this to me? Thanks!

> Unable to get AMRMToken in unmanaged AM when using a secure cluster
> -------------------------------------------------------------------
>
>                 Key: YARN-2892
>                 URL: https://issues.apache.org/jira/browse/YARN-2892
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Sevada Abraamyan
>            Assignee: Rohith
>
> An AMRMToken is retrieved from the ApplicationReport by the YarnClient. 
> When the RM creates the ApplicationReport and sends it back to the client it makes a
simple security check whether it should include the AMRMToken in the report (See createAndGetApplicationReport
in RMAppImpl).This security check verifies that the user who submitted the original application
is the same user who is requesting the ApplicationReport. If they are indeed the same user
then it includes the AMRMToken, otherwise it does not include it.
> The problem arises from the fact that when an application is submitted, the RM  saves
the short username of the user who created the application (See submitApplication in ClientRmService).
Afterwards when the ApplicationReport is requested, the system tries to match the full username
of the requester against the previously stored short username. 
> In a secure cluster using Kerberos this check fails because the principle is stripped
from the username when we request a short username. So for example the short username might
be "Foo" whereas the full username is "Foo@Company.com"
> Note: A very similar problem has been previously reported ([Yarn-2232|https://issues.apache.org/jira/browse/YARN-2232])



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message