[jira] [Resolved] (HDFS-6049) Web UI: Browse file system from data node will fail with secured HDFS

["Haohui Mai (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Haohui Mai resolved HDFS-6049.
------------------------------
    Resolution: Not a Problem

This is no longer an issue after HDFS-6252 is merged into branch-2.

> Web UI: Browse file system from data node will fail with secured HDFS 
> ----------------------------------------------------------------------
>
>                 Key: HDFS-6049
>                 URL: https://issues.apache.org/jira/browse/HDFS-6049
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.5-alpha, 2.2.0
>            Reporter: stanley shi
>
> On a secured HDFS, the webUI for the Active Namenode will display, but when you select a Live Datanode, the browser displays an error and does not display datanode information. It does list a link to "Logs" but when you click on that you get an unauthorized error message.
> When user click on the "live nodes" link on the namenode webui, it goes to "dfsnodelist.jsp" to show the list of datanodes;
> on top half of the "dfsnodelist.jsp" page, you can choose to "browse the filesystem", which direct user to the link "http://*:50070/nn_browsedfscontent.jsp", and this "nn_browsedfscontent.jsp" will redirect user to a random datanode "http://:1006/browseDirectory.jsp?namenodeInfoPort=50070&dir=/&delegation=****&nnaddr=192.168.2.201:8020"; note here the "delegation" is added by namenode to the above link; so in this link, user can browse the filesystem;
> On the bottom half of the "dfsnodelist.jsp" page, a list of nodes are shown; when you click on one data node, the page goes to "http://**:1006/browseDirectory.jsp?namenodeInfoPort=50070&dir=%2F&nnaddr=192.168.2.201:8020", without the "delegation" part, so in this link, user will not be able to browse the content of the filesystem, and an error message is shown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)