You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2013/09/26 20:00:07 UTC

[jira] [Commented] (HADOOP-10000) Namenode log directory link is inaccessible in secure cluster

    [ https://issues.apache.org/jira/browse/HADOOP-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779028#comment-13779028 ] 

Jing Zhao commented on HADOOP-10000:
------------------------------------

Since all the corresponding code is in hadoop-common, move this jira here from HDFS.
                
> Namenode log directory link is inaccessible in secure cluster
> -------------------------------------------------------------
>
>                 Key: HADOOP-10000
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10000
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-5217.000.patch, HDFS-5217.001.patch
>
>
> Currently in a secured HDFS cluster, 401 error is returned when clicking the "NameNode Logs" link.
> Looks like the cause of the issue is that the httpServer does not correctly set the security handler and the user realm currently, which causes the httpRequest.getRemoteUser (for the log URL) to return null and later be overwritten to the default web name (e.g., "dr.who") by the filter. In the meanwhile, in a secured cluster the log URL requires the http user to be an administrator. That's why we see the 401 error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira