[
https://issues.apache.org/jira/browse/HDFS-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294023#comment-14294023
]
Arun Suresh commented on HDFS-5796:
-----------------------------------
[~wheat9], [~qwertymaniac],
Thank you both for chiming in..
bq. Is giving every files the world-readable permission a possible workaround?
It looks like the workaround is fully equivalent to using dr. who here?
The latest patch allows the administrator to configure a real user as the
browser proxy (not static dr.who). Since this would be a real valid user, hdfs
admin can apply normal access grants / restrictions on this user... and thus
wont be world readable like dr.who
> 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)
