You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Mugdha Varadkar (JIRA)" <ji...@apache.org> on 2016/06/10 12:34:21 UTC
[jira] [Updated] (AMBARI-17164) Handle Ranger upgrade scenario in
Kerberized env
[ https://issues.apache.org/jira/browse/AMBARI-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mugdha Varadkar updated AMBARI-17164:
-------------------------------------
Attachment: AMBARI-17164.patch
> Handle Ranger upgrade scenario in Kerberized env
> ------------------------------------------------
>
> Key: AMBARI-17164
> URL: https://issues.apache.org/jira/browse/AMBARI-17164
> 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-17164.patch
>
>
> Add this property to ranger-admin-site.xm:
> {code}
> ranger.plugins.{component}.serviceuser=service_user
> {code}
> Add spnego principal and keytab if cluster is kerberized to below properties:
> {code}
> ranger.spnego.kerberos.principal
> ranger.spnego.kerberos.keytab
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)