You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Velmurugan Periasamy (JIRA)" <ji...@apache.org> on 2016/05/19 05:49:12 UTC

[jira] [Updated] (RANGER-977) Ranger KMS default policies should include hdfs & hive

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

Velmurugan Periasamy updated RANGER-977:
----------------------------------------
    Attachment: 0001-RANGER-977-Adding-hdfs-and-hive-policy-items-while-c.patch

> Ranger KMS default policies should include hdfs & hive
> ------------------------------------------------------
>
>                 Key: RANGER-977
>                 URL: https://issues.apache.org/jira/browse/RANGER-977
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 0.5.0
>            Reporter: Sailaja Polavarapu
>            Assignee: Sailaja Polavarapu
>             Fix For: 0.6.0
>
>         Attachments: 0001-RANGER-977-Adding-hdfs-and-hive-policy-items-while-c.patch
>
>
> Currently when Ranger KMS is installed, only keyadmin user has the permissions.
> Users have to manually create user nn and assign policies for this user for the encryption zone creation to work. This should be added by default. Also nn is a kerberos principal which should be mapped to hdfs user, for which default policy should be added after KMS is installed. (with generate_eek and get_matadata operations). Investigate why KMS is not performing this mapping and resolve it. In addition address this use-case for making hive encryption zones work as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)