Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
with JCR-4429 comes a new type of JackrabbitAccessControlList that allows to provide native support for access control management by principal as defined by org.apache.jackrabbit.api.security.JackrabbitAccessControlManager.
now that there exists a new authorization model in Oak (OAK-8190) that implements these extensions, it would be desirable if the repo-init would cover access control management by principal.
note: while the original aim of OAK-8190 was to store permissions for system users (aka service users) separately, the implementation in oak-authorization-principalbased is not limited to system users and doesn't mandate the policies to be stored with a user node. the location of the access controlled node is an implementation detail that can be changed. see Jackrabbit API and http://jackrabbit.apache.org/oak/docs/security/authorization/principalbased.html for additional details.
Attachments
Attachments
Issue Links
- blocks
-
SLING-8722 Documentation for SLING-8602 and SLING-8619
- Resolved
- is blocked by
-
SLING-8619 RepoInitGrammer: Add repository-level marker to pathsList
- Closed
-
SLING-8625 org.apache.sling.testing.sling-mock-oak : update oak version to 1.16.0, jackrabbit version to 2.18.2
- Closed
-
SLING-8627 Update sling-jcr-repoinit to Oak 1.16.0 and Jackrabbit 2.18.2
- Closed
- is related to
-
SLING-8617 GeneralAclTest: test session should be refreshed to reflect latest changes
- Open
-
SLING-8604 AclUtil.setAcl: invalid assumptions regarding principal lookup
- Closed
-
SLING-8605 AclUtil.createLocalRestrictions should use JackrabbitAccessControlList.isMultiValueRestriction(String)
- Closed
-
SLING-8621 TestUtil.cleanup causes in WARNing due to SlingContext Rule
- Closed