[
https://issues.apache.org/jira/browse/OAK-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607489#comment-13607489
]
angela commented on OAK-444:
----------------------------
currently the implementation covers most of the version store s.str.
- reading adding version history and versions depends on versionmgt permission
on the corresponding versionable node
- adding intermediate version storage nodes will not be explicitly checked for
permissions instead
the permission validator will check on the version history that is being
added (and fail if there is
not version history).
- reading intermediate version storage nodes: TODO
- activities and activity storage: TODO
- configurations and configuration storage: TODO
> Authorization for the jcr version store
> ---------------------------------------
>
> Key: OAK-444
> URL: https://issues.apache.org/jira/browse/OAK-444
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: angela
> Assignee: angela
>
> as explained in JCR-2963 the version store needs special attention when
> it comes to access control and permissions enforced on the store.
> for oak we need to define mechanisms on how to control access to the
> version store and provide the possibility to limit access to individual
> parts of the version store. some possibilities are already listed in JCR-2963.
> additional topics include:
> - searching for versioned content
> - find and restore versions that have no corresponding versionable node in
> the content tree
> - ability to prevent access to version store altogether without preventing
> access to versions/version histories through JCR version operations
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
