Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-12343

Ambari storm deployment fails in secure mode due to storm principal name

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.1.0
    • 2.1.1
    • ambari-server
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rlevas Robert Levas
            sriharsha Harsha
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment