hadoop-common-issues mailing list archives

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

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

John Zhuge commented on HADOOP-14060:
-------------------------------------

[~xiaochen] HADOOP-13119 does not fix this issue because I just tested in SSL+Kerberos mode,
/logs is still wide open for KMS and HttpFS, while the other servlets return error {{Authentication
required}}. I don't think any follow up such as HADOOP-14077 provides the fix either.

> 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