[
https://issues.apache.org/jira/browse/HDFS-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498444#comment-14498444
]
Haohui Mai commented on HDFS-8155:
----------------------------------
I think that there are two use cases here:
* Using WebHDFS in UI
* Using WebHDFS programmatically (e.g., through {{WebHdfsFileSystem}})
For the first use case -- WebHDFS now recognizes the auth cookie of the UI
therefore the UI works as long as any third-party filter behaves correctly
w.r.t. the UI pages.
For the second use case -- WebHDFS is designed to use DT as the authentication
method. To authenticate, the third-party filter (OAuth2 filter included) should
control when to issue a DT when getting the {{GETDELEGATIONTOKEN}} call. The DT
needs to be presented to the server in all subsequent usages.
I don't think injecting any third-party payload (e.g., OAuth tokens) into
WebHdfsFileSystem make sense.
> Support OAuth2 authentication in WebHDFS
> ----------------------------------------
>
> Key: HDFS-8155
> URL: https://issues.apache.org/jira/browse/HDFS-8155
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: webhdfs
> Reporter: Jakob Homan
> Assignee: Kai Zheng
>
> WebHDFS should be able to accept OAuth2 credentials.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
