Hi Angela, On Tue, 2020-08-25 at 07:39 +0000, Angela Schreiber wrote: > hi robert > > without having a closer look, i would suspect that your repository > comes with default import-behavior configuration that strictly > follows JCR specification which mandates a given principal to exist > when dealing with access control management. oak comes with a variety > of import-behavior options and if you configure it to be > 'besteffort', it will allow to create ACEs for principals, which do > not yet exist.
That does help, thank you. I've swiched the Sling Starter to use this configuration from now on. Best regards, Robert > > hope that helps > angela > ________________________________ > From: Robert Munteanu <[email protected]> > Sent: Friday, August 21, 2020 6:47 PM > To: [email protected] <[email protected]> > Subject: [filevault] Installing users and access control entries in > the same package > > Hi, > > I am trying to install a content package that includes: > > - two users under /home/users/slingshot > - content with ACEs that reference the two users under > /content/slingshot > > When installing the content packages I see that the /content entry is > processed first, leading to errors like > > E /content/slingshot/users/slingshot1/rep:policy > ! org.xml.sax.SAXException: > javax.jcr.security.AccessControlException: Unknown principal > slingshot1 > javax.jcr.security.AccessControlException: Unknown principal > slingshot1 > > and only later on is the user created > > - /home > - /home/users > A /home/users/slingshot > A /home/users/slingshot/slingshot1 > > Obviously, reinstalling the content package fixes the problem but I'm > looking for a more error-safe way of installing the content package. > > How can I install this content package with users and ACEs from > without > errors? > > Thanks, > Robert >
