Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 1 Jul 2016 13:38:11 +0000 (UTC)
From: "Mugdha Varadkar (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12986172.1467378993000.4725.1467380291038@Atlassian.JIRA>
In-Reply-To: <JIRA.12986172.1467378993000@Atlassian.JIRA>
References: <JIRA.12986172.1467378993000@Atlassian.JIRA> <JIRA.12986172.1467378993176@arcas>
Subject: [jira] [Updated] (AMBARI-17522) Handle Ranger Kms upgrade in
 kerberos env
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 01 Jul 2016 13:38:12 -0000


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

Mugdha Varadkar updated AMBARI-17522:
-------------------------------------
    Status: Patch Available  (was: In Progress)

> Handle Ranger Kms upgrade in kerberos env
> -----------------------------------------
>
>                 Key: AMBARI-17522
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17522
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17522.patch
>
>
> *Problem*:
> Upgrade from 2.4 to 2.5 will not have rangerkms principal/keytab identity (as it is added in stack 2.5) to create/get repository from Ranger Service.
> Ranger KMS service had spnego principal/keytab identity in 2.4.
> Ranger KMS service is a dependent on Ranger Service. For previous stack all calls were using urllib2 authentication to create/get repository in Ranger Service in kerberos env. Ranger Service participate in kerberos from 2.5 onwards so all call to create/get repository will be using curl --negotiate.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)