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/04/30 09:17:00 UTC
[jira] [Resolved] (OAK-8284) Improvements to EntryPredicate
[ https://issues.apache.org/jira/browse/OAK-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved OAK-8284.
-------------------------
Resolution: Fixed
Fix Version/s: 1.14.0
[~stillalex], as discussed proposed changes committed at revision 1858411.
> Improvements to EntryPredicate
> ------------------------------
>
> Key: OAK-8284
> URL: https://issues.apache.org/jira/browse/OAK-8284
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, security
> Reporter: angela
> Assignee: angela
> Priority: Minor
> Fix For: 1.14.0
>
> Attachments: EntryPredicate.patch
>
>
> [~stillalex], while working on overall coverage of the permission evaluation code base i found {{org.apache.jackrabbit.oak.security.authorization.permission.EntryPredicate}} confusing and hard to understand. attached patch contains an attempt to simplify and improve this class central to permission evaluation by completely separating the 3 major cases:
> - evaluation for repository level (no path, no tree),
> - evaluation based on a non-null path and finally
> - evaluation based on a non-null tree object and an optional property.
> feedback welcome.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)