You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2019/05/03 09:26:00 UTC

[jira] [Comment Edited] (JCR-4429) Add extension of JackrabbitAccessControlList bound to a principal

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

angela edited comment on JCR-4429 at 5/3/19 9:25 AM:
-----------------------------------------------------

[~stillalex], as discussed i committed the patch at revision 1858564. and ProviderType annotation at rev 1858566



was (Author: anchela):
[~stillalex], as discussed i committed the patch at revision 1858564.


> Add extension of JackrabbitAccessControlList bound to a principal
> -----------------------------------------------------------------
>
>                 Key: JCR-4429
>                 URL: https://issues.apache.org/jira/browse/JCR-4429
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-api
>            Reporter: angela
>            Assignee: angela
>            Priority: Major
>             Fix For: 2.20, 2.19.3
>
>         Attachments: JCR-4429-2.patch, JCR-4429.patch
>
>
> while {{JackrabbitAccessControlManager}} supports editing policies by principals since quite some time, available set of access control policies didn't provide a variant that was naturally bound to a given principal. the attached patch would introduce an extension of {{AccessControlList}} that was actually bound to a principal.
> [~stillalex], i would appreciate if you had time to take a look at the proposed extension. anything missing in terms of contract? does it make sense?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)