hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuanbo Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14060) KMS /logs servlet should have access control
Date Tue, 21 Feb 2017 10:16:44 GMT

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

Yuanbo Liu commented on HADOOP-14060:
-------------------------------------

The filter chain of {{/logs}} is 
{code}
NoCacheFilter->safety->static_user_filter
{code}
while the filter chain of {{/jmx}} is
{code}
NoCacheFilter->safety->static_user_filter->authFilter->MDCFilter
{code}
The authFilter requires kerberos authentication, that's why the responses of {{/jmx}} and
{{/logs}} are different.

> KMS /logs servlet should have access control
> --------------------------------------------
>
>                 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-alpha3
>            Reporter: John Zhuge
>            Assignee: John Zhuge
>
> 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
(v6.3.15#6346)

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


Mime
View raw message