Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 1 Dec 2012 06:09:58 +0000 (UTC)
From: "Bikas Saha (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <1817840380.48470.1354342198353.JavaMail.jiratomcat@arcas>
Subject: [jira] [Moved] (YARN-255) Support secure AM launch for unmanaged
 AM's
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bikas Saha moved MAPREDUCE-4472 to YARN-255:
--------------------------------------------

    Affects Version/s:     (was: 3.0.0)
                       3.0.0
                  Key: YARN-255  (was: MAPREDUCE-4472)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> Support secure AM launch for unmanaged AM's
> -------------------------------------------
>
>                 Key: YARN-255
>                 URL: https://issues.apache.org/jira/browse/YARN-255
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>
> Currently unmanaged AM launch does not get security tokens because tokens are passed by the RM to the AM via the NM during AM container launch. For unmanaged AM's the RM can send tokens in the SubmitApplicationResponse to the secure client. The client can then pass these onto the AM in a manner similar to the NM. 

--
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