[
https://issues.apache.org/jira/browse/HDFS-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318561#comment-14318561
]
Allen Wittenauer edited comment on HDFS-5796 at 2/12/15 5:12 PM:
-----------------------------------------------------------------
Considering we just hit what I suspect is this exact issue... a point of
clarification:
* We have a custom auth plugin
* We are trying to use the new WebHDFS-based UI
* We get an authorization failure
* Switch to old DFS RPC-based UI
* It works
Is this patch/JIRA supposed to fix/be this issue and the discussion has just
veered off or are we looking at HDFS-5716 just not actually working?
was (Author: aw):
So, a point of clarification:
* We have a custom auth plugin
* We are trying to use the new WebHDFS-based UI
* We get an authorization failure
* Switch to old DFS RPC-based UI
* It works
Is this patch/JIRA supposed to fix/be this issue and the discussion has just
veered off or are we looking at HDFS-5716 just not actually working?
> The file system browser in the namenode UI requires SPNEGO.
> -----------------------------------------------------------
>
> Key: HDFS-5796
> URL: https://issues.apache.org/jira/browse/HDFS-5796
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Kihwal Lee
> Assignee: Arun Suresh
> Attachments: HDFS-5796.1.patch, HDFS-5796.1.patch, HDFS-5796.2.patch,
> HDFS-5796.3.patch, HDFS-5796.3.patch
>
>
> After HDFS-5382, the browser makes webhdfs REST calls directly, requiring
> SPNEGO to work between user's browser and namenode. This won't work if the
> cluster's security infrastructure is isolated from the regular network.
> Moreover, SPNEGO is not supposed to be required for user-facing web pages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
