[
https://issues.apache.org/jira/browse/JCRVLT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005527#comment-15005527
]
Tobias Bocanegra commented on JCRVLT-61:
----------------------------------------
maybe I wasn't clear enough:
bq. ... so it is not possible to just add 1 new ACE to the existing set of ACEs
of 1 principal
i.e. _merge_ only works on a per principal level. it replaces all ACEs of a
principal with the ones included in the package. the ACEs of other principals
are left alone. that's why you can't remove the ACEs of principals (since you
would need to include an ACE for the replacement to kick in).
example:
Existing:
p1 - allow - jcr:all
p1 - deny - rep:write
p2 - allow - jcr:all
merge with:
p2 - deny - jcr:read
result:
p1 - allow - jcr:all
p1 - deny - rep:write
p2 - deny - jcr:read
> Allow AccessControllHandling be defined per filter root
> -------------------------------------------------------
>
> Key: JCRVLT-61
> URL: https://issues.apache.org/jira/browse/JCRVLT-61
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Reporter: Tobias Bocanegra
>
> the current packaging only allows to specify the AccessControllHandling per
> package. if one requires different behaviors for different content trees, the
> only workaround today is to create sub-packages.
> it would be nice if the ac-control handling can be defined by workspace
> filter root, similar to the iImportMode - or even tie the
> AccessControllHandling to the ImportMode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
