[
https://issues.apache.org/jira/browse/HADOOP-10832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062362#comment-14062362
]
Varun Vasudev commented on HADOOP-10832:
----------------------------------------
The reason for the
change(https://issues.apache.org/jira/browse/HADOOP-10799?focusedCommentId=14059272&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14059272):
{quote}
Alejandro Abdelnur I'm not sure if this is the right ticket but it would be
preferable to pass tokens as headers instead of URL parameters. URLs can get
logged and passed on as part of the referrer header which exposes the
delegation token. In addition, users can pass around links with delegation
tokens by mistake. YARN-2247(waiting to be reviewed) also implements auth using
delegation tokens for the RM web services but passes the tokens as a header. My
plan was to file a ticket to shift the TimelineServer auth to the header model
once YARN-2247 got committed. I'd be happy to hear your thoughts.
{quote}
> Add support for passing delegation tokens via headers for web services
> ----------------------------------------------------------------------
>
> Key: HADOOP-10832
> URL: https://issues.apache.org/jira/browse/HADOOP-10832
> Project: Hadoop Common
> Issue Type: Task
> Reporter: Varun Vasudev
> Assignee: Varun Vasudev
>
> HADOOP-10799 refactors the WebHDFS code to handle delegation tokens a part of
> hadoop-common. We should add support to pass delegation tokens as a header
> instead of passing it as part of the url.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
