[
https://issues.apache.org/jira/browse/AMBARI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620930#comment-14620930
]
Hudson commented on AMBARI-12343:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #199 (See
[https://builds.apache.org/job/Ambari-branch-2.1/199/])
AMBARI-12343. Ambari storm deployment fails in secure mode due to storm
principal name (rlevas) (rlevas:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fe6afcac990745dcb22433ed0b2d41a64b5f1733)
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/kerberos.json
* ambari-web/app/assets/data/stacks/HDP-2.1/service_components.json
> Ambari storm deployment fails in secure mode due to storm principal name
> ------------------------------------------------------------------------
>
> Key: AMBARI-12343
> URL: https://issues.apache.org/jira/browse/AMBARI-12343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Sriharsha Chintalapani
> Assignee: Robert Levas
> Priority: Blocker
> Fix For: 2.1.0
>
> Attachments: AMBARI-12343-v1.patch, AMBARI-12343.patch,
> AMBARI-12343_01.patch
>
>
> Storm cannot dynamically translate Kerberos principal names to local account
> ids using common auth-to-local rules. It can only strip the realm portion of
> the principal and use that value as the local user id. Because of this,
> automatically adding the cluster name to the principal name of the Storm user
> Kerberos Identity will lead to issues for Storm. Therefore the default
> behavior for generating the Storm user's Kerberos should be to use the
> storm-env/storm_user value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
