[
https://issues.apache.org/jira/browse/RANGER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhay Kulkarni updated RANGER-2481:
-----------------------------------
Description:
Ranger supports tag-based policies out of the box. However, there are a few
configuration steps that need to be performed in order to set up Ranger to
perform tag-based authorization. As these steps are often missed, it will be
useful to provide a commonly used/structured way of automatically creating tag
service and linking it to resource service.
This may be controlled through few configuration parameters:
ranger.tagservice.auto.create=<true|false> ==> If tag-service needs to be
created when resource-service is created.
ranger.tagservice.auto.name=<tag-service-name> ==> If value is specified, then
it is used to name the tag-service, otherwise the name of tag-service is
constructed from the name of the resource-service (by replacing the part after
last '_' by string 'tag', and if there is no '_' character in the
resource-service name, then tag-service is not created/linked with
resource-service).
ranger.tagservice.auto.link=<true|false> ==> Used only if
ranger.tagservice.auto.create is true. Set to true only if resource-service
needs to be linked to the tag-service
was:
Ranger supports tag-based policies out of the box. However, there are a few
configuration steps that need to be performed in order to set up Ranger to
perform tag-based authorization. As these steps are often missed, it will be
useful to provide a commonly used/structured way of automatically creating tag
service and linking it to resource service.
This may be controlled through few configuration parameters:
ranger.tagservice.auto.create=<true|false> ==> If tag-service needs to be
created when resource-service is created.
ranger.tagservice.auto.name=<tag-service-name> ==> If value is specified, then
it is used to name the tag-service, otherwise the name of tag-service is
constructed from the name of the resource-service (by replacing the part after
last '_' by string 'tag', and if there is no '_' character in the
resource-service name, then tag-service is not created/linked with
resource-service).
ranger.tagservice.auto.link=<true|false> ==> If resource-service needs to be
linked to the tag-service
> Create a tag service when a resource service is created and link it to
> resource service
> ---------------------------------------------------------------------------------------
>
> Key: RANGER-2481
> URL: https://issues.apache.org/jira/browse/RANGER-2481
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: 2.0.0
>
>
> Ranger supports tag-based policies out of the box. However, there are a few
> configuration steps that need to be performed in order to set up Ranger to
> perform tag-based authorization. As these steps are often missed, it will be
> useful to provide a commonly used/structured way of automatically creating
> tag service and linking it to resource service.
> This may be controlled through few configuration parameters:
> ranger.tagservice.auto.create=<true|false> ==> If tag-service needs to be
> created when resource-service is created.
> ranger.tagservice.auto.name=<tag-service-name> ==> If value is specified,
> then it is used to name the tag-service, otherwise the name of tag-service is
> constructed from the name of the resource-service (by replacing the part
> after last '_' by string 'tag', and if there is no '_' character in the
> resource-service name, then tag-service is not created/linked with
> resource-service).
> ranger.tagservice.auto.link=<true|false> ==> Used only if
> ranger.tagservice.auto.create is true. Set to true only if resource-service
> needs to be linked to the tag-service
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
