You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2016/05/31 08:05:12 UTC

[jira] [Created] (RANGER-1003) Handle Ranger upgrade scenario in Kerberized Cluster

Gautam Borad created RANGER-1003:
------------------------------------

             Summary: 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


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)