[jira] [Updated] (SLING-9412) AclUtil.containsEquivalentEntry should not fail if no such node exists

["Angela Schreiber (Jira)" <ji...@apache.org>]

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

Angela Schreiber updated SLING-9412:
------------------------------------
    Attachment: SLING-9412.patch

> AclUtil.containsEquivalentEntry should not fail if no such node exists
> ----------------------------------------------------------------------
>
>                 Key: SLING-9412
>                 URL: https://issues.apache.org/jira/browse/SLING-9412
>             Project: Sling
>          Issue Type: Bug
>          Components: Repoinit
>            Reporter: Angela Schreiber
>            Priority: Minor
>         Attachments: SLING-9412.patch
>
>
> {{AclUtil.setPrincipalAcl}} has been adjusted with SLING-8766 to be more lenient with principals that don't support principal-based access control setup. However, the check for equivalent resource-based setup still fails if no node exists for the given absolute path (lookup of policies will fail with {{PathNotFoundException}}. to reduce the potential repo-init failures we should additionally verify that there exists a node before trying to verify the resource-based ac-setup.



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