[
https://issues.apache.org/jira/browse/AMBARI-17522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-17522:
-------------------------------------
Description:
*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.
was:
*Problem*:
Upgrade from 2.4 to 2.5 will not have rangerkms principal/keytab available to
create/get repository from Ranger Admin. Ranger KMS was using spnego
principal/keytab in 2.4. Will be using that.
> 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
>
>
> *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)
