[ 
https://issues.apache.org/jira/browse/ATLAS-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chaitali borole updated ATLAS-4717:
-----------------------------------
    Description: 
https://issues.apache.org/jira/browse/ATLAS-4717
Create tag - ptag
Associate ptag to entity e1
in detailsPage of  entity e1 , tag is visible.

For user admin

Deny permissions to create , read , update , delete classification types.

Visit entity e1 as admin user.
So here classification is still visible when associated with entities on search 
page as well as details page
Only classification under the classifications tab on UI are hidden.

  was:
Create tag - ptag
Create tag - ctag with parent tag as ptag
Associate ctag to entity e1
in detailsPage of  entity e1 , ctag@ptag is seen.

For user admin

Deny permissions to create , read , update , delete classification types.

Visit entity e1 as admin user.

Now only ctag is seen instead of ctag@ptag

When search page is loaded after the deny policy we cannot access entity
As entitydef is empty in the response 


> When user doesn't have CRUD permission on classification , classification tag 
> is still shown on detailsPage
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-4717
>                 URL: https://issues.apache.org/jira/browse/ATLAS-4717
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: chaitali borole
>            Assignee: chaitali borole
>            Priority: Major
>
> https://issues.apache.org/jira/browse/ATLAS-4717
> Create tag - ptag
> Associate ptag to entity e1
> in detailsPage of  entity e1 , tag is visible.
> For user admin
> Deny permissions to create , read , update , delete classification types.
> Visit entity e1 as admin user.
> So here classification is still visible when associated with entities on 
> search page as well as details page
> Only classification under the classifications tab on UI are hidden.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to