You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2020/08/03 17:10:00 UTC

[jira] [Closed] (SLING-8810) DeleteAce response to remove a non-existing ACE is not consistent

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

Eric Norman closed SLING-8810.
------------------------------

Completed with the 3.0.6 release

> DeleteAce response to remove a non-existing ACE is not consistent
> -----------------------------------------------------------------
>
>                 Key: SLING-8810
>                 URL: https://issues.apache.org/jira/browse/SLING-8810
>             Project: Sling
>          Issue Type: Bug
>    Affects Versions: JCR Jackrabbit Access Manager 3.0.4
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: JCR Jackrabbit Access Manager 3.0.6
>
>
> When an attempt is made to remove a non-existing ACE via a DeleteAce request, the response is not consistent.
>  # When an AccessControlList doesn't exist, a "Unable to find or create an access control policy to update ..." exception is thrown
>  # When an AccessControlList does exist but is empty, no exception is thrown
>  # When an AccessControlList exists but there is no ACE for the submitted principalId, no exception is thrown
>  
>  
> Expected:
> To be consistent, the #1 scenario above should behave the same as #2 and #3 and just do nothing and not throw the exception.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)