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

Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2015/06/02 20:28:49 UTC

[jira] [Assigned] (YARN-3761) Set delegation token service address at the server side

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

Varun Saxena reassigned YARN-3761:
----------------------------------

    Assignee: Varun Saxena

> Set delegation token service address at the server side
> -------------------------------------------------------
>
>                 Key: YARN-3761
>                 URL: https://issues.apache.org/jira/browse/YARN-3761
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: security
>            Reporter: Zhijie Shen
>            Assignee: Varun Saxena
>
> Nowadays, YARN components generate the delegation token without the service address set, and leave it to the client to set. With our java client library, it is usually fine. However, if users are using REST API, it's going to be a problem: The delegation token is returned as a url string. It's so unfriendly for the thin client to deserialize the url string, set the token service address and serialize it again for further usage. If we move the task of setting the service address to the server side, the client can get rid of this trouble.



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