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/11/11 11:44:18 UTC

[jira] [Commented] (OAK-951) Consider implementing regular access control operations for ReadPolicy

    [ https://issues.apache.org/jira/browse/OAK-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818852#comment-13818852 ] 

angela commented on OAK-951:
----------------------------

while implementing this doesn't have too much priority IMO, it can be looked as a POC for implementing custom policies such as e.g. being used for providing closed user group setup -> moving this to a separate issue in order not to block resolution of the general "implement access control management" task.

> Consider implementing regular access control operations for ReadPolicy
> ----------------------------------------------------------------------
>
>                 Key: OAK-951
>                 URL: https://issues.apache.org/jira/browse/OAK-951
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: angela
>            Assignee: angela
>             Fix For: 0.15
>
>
> currently the new ReadPolicy are defined by the permission configuration and cannot be managed using regular access control management operations such
> as getApplicablePolicies, setPolicy, removePolicy.
> the current code should be refactored such that not only getPolicies/getEffectivePolicies support that specific policy type.
> the configuration may still be used for the original setup but subsequent management should be possible with the regular ac mgt api.



--
This message was sent by Atlassian JIRA
(v6.1#6144)