[
https://issues.apache.org/jira/browse/RANGER-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhay Kulkarni resolved RANGER-1321.
------------------------------------
Resolution: Fixed
Fix Version/s: master
Patch (available at the review board : https://reviews.apache.org/r/57303/)
Commit details:
Project: http://git-wip-us.apache.org/repos/asf/ranger/repo
Commit: http://git-wip-us.apache.org/repos/asf/ranger/commit/85ddb48e
Tree: http://git-wip-us.apache.org/repos/asf/ranger/tree/85ddb48e
Diff: http://git-wip-us.apache.org/repos/asf/ranger/diff/85ddb48e
Branch: refs/heads/master
Commit: 85ddb48e2c7a795969e908ebce377ab4666aecce
Parents: 0ad9539
> 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
> Fix For: master
>
>
> 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)
