[
https://issues.apache.org/jira/browse/RANGER-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Gupta resolved RANGER-5794.
----------------------------------
Fix Version/s: 3.0.0
2.10
Resolution: Fixed
> 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
> Fix For: 3.0.0, 2.10
>
> 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)
