[
https://issues.apache.org/jira/browse/YARN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753378#comment-13753378
]
Bikas Saha commented on YARN-707:
---------------------------------
please feel free to define this where it makes most sense. The existing
AM_RM_TOKEN_SERVICE is a stop gap to be fixed via YARN-986. If you want, then
please move it also.
{code}
AM_CLIENT_TOKEN_MASTER_KEY_NAME
{code}
Is there a way for us to check that the clientAMSecretManager also got
refreshed with the same key?
{code}
+ // assert client token master key is recovered back to api-versioned
+ // client token master key
+ Assert.assertEquals("client token master key not restored",
+ attempt1.getClientTokenMasterKey(),
+ loadedAttempt1.getClientTokenMasterKey());
{code}
For the rest I will defer to comments from previous reviewers.
> 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
>
>
> 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
