[jira] [Updated] (SLING-9690) Configure best-effort import behaviour for access control items

["Oliver Lietz (Jira)" <ji...@apache.org>]

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

Oliver Lietz updated SLING-9690:
--------------------------------
    Component/s: Karaf

> Configure best-effort import behaviour for access control items
> ---------------------------------------------------------------
>
>                 Key: SLING-9690
>                 URL: https://issues.apache.org/jira/browse/SLING-9690
>             Project: Sling
>          Issue Type: Improvement
>          Components: Karaf, Starter
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Starter 12
>
>
> When importing principals and access control entries in the same package there are some scenarios that don't work out-of-the-box with FileVault content packages
> - users and resource-based ACEs in the same content package; users are not guaranteed to be processed before ACEs ( see [oak-dev@jacrabbit.apache.org: Installing users and access control entries in the same package|https://lists.apache.org/thread.html/r94b8b31d3da59d18e3eaced1594c453fc7759b62d26474a42c3dbbe3%40%3Coak-dev.jackrabbit.apache.org%3E] )
> - users and principal-based ACEs in the same content package ( see JCRVLT-472 )
> A reasonable workaround for this kind of scenarios is to configure {{AuthorizationConfigurationImpl}} to have a "besteffort" import behaviour.



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