[
https://issues.apache.org/jira/browse/RANGER-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138691#comment-18138691
]
Rakesh Gupta commented on RANGER-5794:
--------------------------------------
*Merged into apache master* :
https://github.com/apache/ranger/commit/fca19acd22aecaa3502e91ea60a11e69ea088d12
{*}Merged into ranger-2.10{*}:
https://github.com/apache/ranger/commit/0520290ab406e4514048a9972b6dce00d9fe5157
> Atlas permissions reappear in tag policies when enableTagBasedPolicies is
> disabled
> ----------------------------------------------------------------------------------
>
> Key: RANGER-5794
> URL: https://issues.apache.org/jira/browse/RANGER-5794
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Rakesh Gupta
> Assignee: Rakesh Gupta
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Problem:*
> After RANGER-4805, Atlas permissions ({{{}atlas:read{}}}, etc.) can still
> appear in tag policies and in {{{}x_access_type_def{}}}, especially after
> RANGER-3491 changed the service-definition bootstrap flow.
> *Cause:*
> The {{enableTagBasedPolicies}} check was only present in
> {{{}updateTagServiceDefForAccessTypes(){}}}, which is no longer called from
> the production code. The actual sync path ({{{}postCreate{}}} /
> {{postUpdate}} → {{{}updateTagServiceDefForUpdatingAccessTypes(){}}}) did not
> have this check, allowing Atlas permissions to be synced into the tag
> service-definition.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
