You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2013/04/19 16:41:16 UTC
[jira] [Commented] (OAK-444) Authorization for the jcr version
store
[ https://issues.apache.org/jira/browse/OAK-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636432#comment-13636432 ]
angela commented on OAK-444:
----------------------------
completing this is currently blocked by the fact that all version mgt is
currently disabled.
> 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