[
https://issues.apache.org/jira/browse/RANGER-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahesh Hanumant Bandal reassigned RANGER-3314:
----------------------------------------------
Assignee: Mahesh Hanumant Bandal
> [Atlas Ranger Plugin classification auth changes] Importing atlas policy with
> old schema displays incorrect permissions on UI
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-3314
> URL: https://issues.apache.org/jira/browse/RANGER-3314
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 2.2.0
> Reporter: Abhishek Shukla
> Assignee: Mahesh Hanumant Bandal
> Priority: Major
> Attachments: permission list.png, policy details.png, policy.json
>
>
> This is with respect to RANGER-3195 where we have moved the Add/Update/Remove
> classification permissions to a new classification resource.
>
> Steps:
> * Try to import an atlas resource policy with the old format [Attached test
> policy.json]
> * Expectations are the permission like Add/Update/Remove classification
> should not be shown in permission list as they are not present at Entity
> resource level but we are showing them in the UI. [Attached screenshots]
>
> So these permissions are present in the policy, is this expected? I have not
> performed any atlas side validation to check if these permissions will be
> enforced.
> I think we should not add these permissions even if they are present in the
> policy OR we should display some error message during import, displaying
> permissions not supported something like that.
>
> Creating this Jira for more discussion on this.
> cc [~nixon]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
