[ 
https://issues.apache.org/jira/browse/ATLAS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276628#comment-15276628
 ] 

Hemanth Yamijala commented on ATLAS-497:
----------------------------------------

Tested ATLAS-497.9.patch in the following scenarios:

* With default policy settings in {{policy-store.txt}}, admin user is able to 
do all operations.
* Changed resource type rule for admin user to remove some resource types and 
verified that those resources cannot be accessed.
* Changed allowed operations rule for admin user to removed some operations, 
and verified those operations cannot be performed.
* Verified hive hook is working fine (no dependency on user for this).

Will commit this patch now.

> Simple Authorization
> --------------------
>
>                 Key: ATLAS-497
>                 URL: https://issues.apache.org/jira/browse/ATLAS-497
>             Project: Atlas
>          Issue Type: New Feature
>    Affects Versions: 0.7-incubating
>            Reporter: Erik Bergenholtz
>            Assignee: Saqeeb Shaikh
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-497.1.patch, ATLAS-497.2.patch, ATLAS-497.6.patch, 
> ATLAS-497.7.patch, ATLAS-497.8.patch, ATLAS-497.9.patch, ATLAS-497.patch
>
>
> Atlas needs to support a simple (out of box) authorization mechanism.
> Defined Roles:
> - Data Scientist: provides a read only view (GET)
> - Data Steward: provides a read/edit view (PUT, POST, DELETE)
> - Admin (can do anything)
> All can comment on entity
> Requirements
> - Atlas will implement a simple file based store for providing user to role 
> mapping
> - The out of box experience will be this file based mechanism for 
> authorization



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

Reply via email to