[
https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290749#comment-17290749
]
Dharshana M Krishnamoorthy commented on ATLAS-3976:
---------------------------------------------------
Update:
This is reproducible on struct, entity and relationship types. It works fine on
classification, business_metadata and enum types
{code:java}
{'errorCode': 'ATLAS-409-00-001', 'errorMessage': 'Given type
read_auth_struct_zEFBP already exists'} {code}
{code:java}
{'errorCode': 'ATLAS-409-00-001', 'errorMessage': 'Given type
read_auth_entity_EfAyL already exists'} {code}
{code:java}
{'errorCode': 'ATLAS-409-00-001', 'errorMessage': 'Given type
non_read_relationship_ENshy already exists'}{code}
> 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: chaitali borole
> 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)
