You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Abhay Kulkarni (JIRA)" <ji...@apache.org> on 2017/03/14 02:42:41 UTC
[jira] [Assigned] (RANGER-1321) Provide a mechanism to create
service-specific default policies
[ https://issues.apache.org/jira/browse/RANGER-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhay Kulkarni reassigned RANGER-1321:
--------------------------------------
Assignee: Abhay Kulkarni (was: Ramesh Mani)
> Provide a mechanism to create service-specific default policies
> ---------------------------------------------------------------
>
> Key: RANGER-1321
> URL: https://issues.apache.org/jira/browse/RANGER-1321
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 0.6.0, 0.7.0
> Reporter: Ramesh Mani
> Assignee: Abhay Kulkarni
>
> When a service is created, Ranger Admin creates a default policy in the new service which grants all access to the user specified in service-config. This works for most services. However, it is possible that some service implementation might want to create default policy with different accesses. It will be useful to provide a mechanism to enable service-specific default policy creation – similar to service-specific resource-lookup implementations which is available today via RangerBaseService interface. Something like:
>
> public abstract class RangerBaseService {
> // ...
>
> public List<RangerPolicy> getDefaultPolicies();
> }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)