[
https://issues.apache.org/jira/browse/OAK-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832099#comment-15832099
]
Chetan Mehrotra commented on OAK-4959:
--------------------------------------
bq. why is it not possible to add the validator in the setup as we do with
others such as e.g. PrivateStoreValidatorProvider
Normal validators do not have access to principal set associated with commit
(CommitInfo only knows about userid). Its only the validators created by
SecurityConfiguration who have access to this information. However currently
its not possible to register a SecurityConfiguration as
SecurityProviderRegistration monitor only the derived configuration services.
One way out would be to modify SecurityProviderRegistration to also monitor
those services which only implement the SecurityConfiguration interface
> Review the security aspect of bundling configuration
> ----------------------------------------------------
>
> Key: OAK-4959
> URL: https://issues.apache.org/jira/browse/OAK-4959
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Labels: bundling
> Fix For: 1.6
>
> Attachments: OAK-4959-v1.patch
>
>
> The config for node bundling feature in DocumentNodeStore is currently stored
> under {{jcr:system/rep:documentStore/bundlor}}. This task is meant to
> * Review the access control aspect - This config should be only updatetable
> by system admin
> * Config under here should be writeable via JCR api
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
