[
https://issues.apache.org/jira/browse/AMBARI-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352964#comment-14352964
]
Hudson commented on AMBARI-9981:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #1981 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1981/])
AMBARI-9981. Ambari storm logviewer in secure mode doesn't work (rlevas)
(rlevas:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c095bd9116d3391b4745adde0ef03b861b4a099c)
*
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params.py
> Ambari storm logviewer in secure mode doesn't work
> --------------------------------------------------
>
> Key: AMBARI-9981
> URL: https://issues.apache.org/jira/browse/AMBARI-9981
> Project: Ambari
> Issue Type: Bug
> Reporter: Robert Levas
> Labels: kerberos
> Attachments: AMBARI-9981_01.patch
>
>
> Storm logviewer uses the same UI.filter config thats being used for Storm UI.
> In secure mode storm UI uses SPENGO to authenticate user to access the UI.
> Similarly logviewer also does the same .
> But in Ambari 1.7 we advise user to create HTTP/storm-ui@REALM and this gets
> added to storm.yaml.
> As this is bound to a host storm logviewers which are running one per
> supervisor won't be able to use this key .
> Solution:
> There is a configuration problem in the {{/etc/storm/conf/storm.yaml}} file.
> In particular the issue is here:
> {code:title=/etc/storm/conf/storm.yaml:109}
> ui.filter.params:
> "type": "kerberos"
> "kerberos.principal": "HTTP/[email protected]"
> "kerberos.keytab": "/etc/security/keytabs/spnego.service.keytab"
> "kerberos.name.rules": "DEFAULT"
> {code}
> The {{kerberos.principal}} value should be the SPNEGO principal for the
> localhost, not the host where the UI server is running. In this example, the
> localhost is *host-4.internal* so the {{kerberos.principal}} value should be
> *HTTP/[email protected]* not *HTTP/[email protected]*.
> The Storm UI server is running on *host-2.internal*
> The fix for this should be in the code around
> {code:title=common-services/STORM/0.9.1.2.1/package/scripts/params.py:103}
> _storm_ui_jaas_principal_name =
> config['configurations']['storm-env']['storm_ui_principal_name']
> storm_ui_host = default("/clusterHostInfo/storm_ui_server_hosts", [])
> storm_ui_jaas_principal =
> _storm_ui_jaas_principal_name.replace('_HOST',storm_ui_host[0].lower())
> {code}
> {{storm_ui_jaas_principal}} is then used in the template to build the
> storm.yaml file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)