You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ankita Sinha (JIRA)" <ji...@apache.org> on 2016/05/31 09:04:13 UTC
[jira] [Updated] (RANGER-1003) Handle Ranger upgrade scenario in
Kerberized Cluster
[ https://issues.apache.org/jira/browse/RANGER-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ankita Sinha updated RANGER-1003:
---------------------------------
Attachment: RANGER-1003.patch
> Handle Ranger upgrade scenario in Kerberized Cluster
> ----------------------------------------------------
>
> Key: RANGER-1003
> URL: https://issues.apache.org/jira/browse/RANGER-1003
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.6.0
> Reporter: Gautam Borad
> Assignee: Ankita Sinha
> Fix For: 0.6.0
>
> Attachments: RANGER-1003.patch
>
>
> In order for Ranger to work in Kerberos env after upgrading from earlier version - make following changes ::
> 1. After upgrade add lookup user to have permissions in all default policy.
> 2. After upgrade add custom property "policy.download.auth.users" and "tag.download.auth.users" in Service config of each repo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)