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 2019/06/06 07:36:00 UTC

[jira] [Resolved] (OAK-8385) Get rid of duplicated AcEntry/Entry in PermissionStoreEditor and AccessControlValidator

     [ https://issues.apache.org/jira/browse/OAK-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved OAK-8385.
-------------------------
       Resolution: Fixed
    Fix Version/s: 1.16.0

Committed revision 1860703.


> Get rid of duplicated AcEntry/Entry in PermissionStoreEditor and AccessControlValidator
> ---------------------------------------------------------------------------------------
>
>                 Key: OAK-8385
>                 URL: https://issues.apache.org/jira/browse/OAK-8385
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, security
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>             Fix For: 1.16.0
>
>
> both {{CommitHooks}} create internal entry classes to keep track and validate of changes made to a given access control policy. I would suggest to refactor the code such that they use the same base class. Note, that {{AccessControlEntry}} is not a great match because it is defined by JCR API while what is needed here is a low level view on a given entry.



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