Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
in a oak setup with immutable mounts we would like to be able to cover system users and their permissions with a separate mount. while setting up a mount for system users is feasible out of the box, this doesn't apply for the default access control content created for the associated system user principals, which due to the nature of the default authorization implementation will be distributed across the repository. in addition any entries created for any system user principal may be collocated in a mutable policy with entries for regular principals and where the order is crucial for the resulting effective permissions.Therefore it would be desirable if in a mount-based setup system users and their permission setup were to be collocated in the same mount.
stillalex, fyi
Attachments
Issue Links
- is blocked by
-
OAK-8212 ImporterImpl.importProperties prone to NPE
- Closed
-
OAK-8155 CompositePermissionProvider: add possibility to abort evaluation
- Closed
-
OAK-8295 Update version of jackrabbit dependency
- Closed
- is broken by
-
OAK-8490 FilterProviderImpl.getFilter may fail if principal cache enabled
- Closed
- is duplicated by
-
OAK-8242 JavaDoc error in oak-authorization-principalbased
- Resolved
- is related to
-
JCRVLT-340 Adjust JackrabbitACLImporter to handle extensions provided by OAK-8190
- Closed
- relates to
-
JCR-4429 Add extension of JackrabbitAccessControlList bound to a principal
- Closed