[
https://issues.apache.org/jira/browse/HDFS-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318856#comment-14318856
]
Allen Wittenauer commented on HDFS-5796:
----------------------------------------
The irony is that our handler is using the AltKerberos code (which means it
does support SPNEGO). However WebHDFS still requires us mucking about with
dfs.web.authentication.filter rather than inherit from the global setting.
HDFS-5716 seems like a bug rather than a feature at this point. :(
(I also found HDFS-7033 while researching why our auth bits aren't working. So
now I feel stupid as well as perplexed trying to get this feature to work.)
> 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)
