[
https://issues.apache.org/jira/browse/OAK-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062830#comment-16062830
]
Alex Deparvu commented on OAK-6356:
-----------------------------------
thanks for the feedback! I've update the wip branch to include all changes :)
bq. trivial: my IDE claims that that the static modifier is redundant
this is interesting. seems to be the case that the static modifier is indeed
not needed [0]:
bq. A nested enum type is implicitly static. It is permitted for the
declaration of a nested enum type to redundantly specify the static modifier.
[0] http://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.9
> Allow CompositePermissionProvider to OR entries
> -----------------------------------------------
>
> Key: OAK-6356
> URL: https://issues.apache.org/jira/browse/OAK-6356
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, security
> Reporter: Alex Deparvu
> Assignee: Alex Deparvu
> Fix For: 1.7.3
>
> Attachments: OAK-6356.patch, OAK-6356-v2.patch
>
>
> Currently the {{CompositePermissionProvider}} ANDs the entries and if any of
> those denies a check, all the chain will fail early. I'd like to extend this
> mechanism to 'OR' items if needed.
> A first application of this ORing could be the multiplexed permission store
> where the default store could deny a check but a mount could allow it, so it
> could be seen as valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
