[
https://issues.apache.org/jira/browse/AMBARI-17522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360852#comment-15360852
]
Gautam Borad commented on AMBARI-17522:
---------------------------------------
Committed to trunk :
https://github.com/apache/ambari/commit/d2a008070d43425d78bd78fdd276c3f37c4f6070
Committed to branch-2.4 :
https://github.com/apache/ambari/commit/a0970a76e3c2dcd3705639cb2f6e73b09250adf6
> 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 in 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)
