ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramesh Mani (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (RANGER-1321) Provide a mechanism to create service-specific default policies
Date Fri, 20 Jan 2017 01:09:26 GMT

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

Ramesh Mani reassigned RANGER-1321:
-----------------------------------

    Assignee: 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: Ramesh Mani
>
> 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.4#6332)

Mime
View raw message