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 Tue, 21 Feb 2017 06:02:44 GMT

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

John Zhuge commented on HADOOP-14060:

Here are my steps to reproduce in a single node SSL+Kerberos setup:
# git clone https://github.com/jzhuge/hadoop-setup-scripts.git, cd {{hadoop-setup-scripts}}
# You may want to replace a few hardcoded strings: GCE.CLOUDERA.COM => YOUR_REALM, jzhuge
# ./create_keytabs <kdc_host> localhost GCE.CLOUDERA.COM
# kinit -t ~/.config/kerberos/hdfs.keytab hdfs/localhost@GCE.CLOUDERA.COM
# export HADOOP_HOME=~/hadoop/hadoop-dist/target/hadoop-3.0.0-alpha3-SNAPSHOT
# ./pseudo_dist start config/secure
# kinit -t ~/.config/kerberos/$USER.keytab $USER@GCE.CLOUDERA.COM
# PATH=$HADOOP_HOME/bin:$PATH TEST_SSL_ENABLED=yes bats ~/hadoop-bats-tests, all tests should
# Open a browser, can not open https://localhost:9600/jmx, error "Authentication required";
however, ok to open https://localhost:9600/logs.

Maybe I miss something in the config files?

> 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

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

View raw message