ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gautam Borad (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17522) Handle Ranger Kms upgrade in kerberos env
Date Mon, 04 Jul 2016 05:32:11 GMT

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

Gautam Borad updated AMBARI-17522:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

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

Mime
View raw message