hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-707) Add user info in the YARN ClientToken
Date Thu, 29 Aug 2013 22:09:52 GMT

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

Jason Lowe updated YARN-707:

    Attachment: YARN-707-20130829.txt

Patch to pass the client user name to getApplicationReport and enhance the restart test to
verify the secret manager also knows about the key after restart.

I left AM_CLIENT_TOKEN_MASTER_KEY_NAME in RMStateStore since there are many reasons why RMAppAttemptImpl
is importing RMStateStore, not just for this constant, and the only reason it needs the constant
is for storage purposes.  Cleaning up the interface between RMAppAttemptImpl and RMStateStore
is another JIRA, IMHO.
> Add user info in the YARN ClientToken
> -------------------------------------
>                 Key: YARN-707
>                 URL: https://issues.apache.org/jira/browse/YARN-707
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Bikas Saha
>            Assignee: Jason Lowe
>            Priority: Blocker
>             Fix For: 3.0.0, 2.1.1-beta
>         Attachments: YARN-707-20130822.txt, YARN-707-20130827.txt, YARN-707-20130828-2.txt,
YARN-707-20130828.txt, YARN-707-20130829.txt
> If user info is present in the client token then it can be used to do limited authz in
the AM.

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

View raw message