hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10000) HttpServer log link is inaccessible in secure cluster
Date Mon, 30 Sep 2013 20:46:27 GMT

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

Suresh Srinivas commented on HADOOP-10000:
------------------------------------------

[~jingzhao], adding documentation of new configuration parameters and also documentation on
how to set it up would help understand this patch better.

> HttpServer log 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message