jsedding commented on PR #45:
URL:
https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/45#issuecomment-1789180598
I have implemented this using the following, option based, syntax:
```
set ACL for nonExistingGroup (ACLOptions=ignoreMissingPrincipal)
allow jcr:read on /
end
```
With this implementation, the current behaviour remains unchanged. Only when
this new option is present, will the check for existence of the principal in
repoinit be skipped. In that case, the behaviour of the repository determines,
what happens.
Does this look acceptable? And could this approach be recommended to be
employed for cases where an external principal is not yet sync'ed into the
repository?
cc @bdelacretaz @anchela @kwin
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
