You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2015/07/09 05:04:05 UTC

[jira] [Assigned] (AMBARI-12343) Ambari storm deployment fails in secure mode due to storm principal name

     [ https://issues.apache.org/jira/browse/AMBARI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Levas reassigned AMBARI-12343:
-------------------------------------

    Assignee: Robert Levas  (was: Sriharsha Chintalapani)

> 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
>
>
> 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)