[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dharshana M Krishnamoorthy updated ATLAS-3976: ---------------------------------------------- Description: hrt_qa has crud permission on business_metadata bm_1 is created by hrt_qa hrt_1 has read-only permission on business_metadata bm_1 When hrt_1 is trying to create bm_1 again, since hrt_1 is a read-only user 403 unauthorised should be thrown, instead 409 conflict is thrown was: hrt_qa has crud permission on classification PII is created by hrt_qa hrt_1 has read-only permission on classification PII When hrt_1 is trying to create PII again, since its a read-only user 403- unauthorised to create should be thrown, instead 409 conflict is thrown > On creating a type with a type_name that already exists as a read-only user > 409 is thrown instead on 403 > --------------------------------------------------------------------------------------------------------- > > Key: ATLAS-3976 > URL: https://issues.apache.org/jira/browse/ATLAS-3976 > Project: Atlas > Issue Type: Bug > Reporter: Dharshana M Krishnamoorthy > Assignee: Nixon Rodrigues > Priority: Major > > hrt_qa has crud permission on business_metadata > bm_1 is created by hrt_qa > hrt_1 has read-only permission on business_metadata bm_1 > When hrt_1 is trying to create bm_1 again, since hrt_1 is a read-only user > 403 unauthorised should be thrown, instead 409 conflict is thrown -- This message was sent by Atlassian Jira (v8.3.4#803005)