hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil Govindan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14060) HTTP servlet /logs should require authentication and authorization
Date Wed, 29 Aug 2018 04:25:00 GMT

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

Sunil Govindan commented on HADOOP-14060:

As this jira is marked for 3.2 as a blocker, cud u pls help to take this forward or move out
if its not feasible to finish in coming weeks. 3.2 code freeze date is nearby in a weeks.
Kindly help to check the same.

cc [~jzhuge] 

> HTTP servlet /logs should require authentication and authorization
> ------------------------------------------------------------------
>                 Key: HADOOP-14060
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14060
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: kms
>    Affects Versions: 3.0.0-alpha4
>            Reporter: John Zhuge
>            Priority: Critical
>         Attachments: HADOOP-14060-tmp.001.patch
> HADOOP-14047 makes KMS call {{HttpServer2#setACL}}. Access control works fine for /conf,
/jmx, /logLevel, and /stacks, but not for /logs.
> The code in {{AdminAuthorizedServlet#doGet}} for /logs and {{ConfServlet#doGet}} for
/conf are quite similar. This makes me believe that /logs should subject to the same access
control as intended by the original developer.
> IMHO this could either be my misconfiguration or there is a bug somewhere in {{HttpServer2}}.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message