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/01/10 15:56:01 UTC

[jira] [Updated] (OAK-7982) ACL.addEntry: check for mandatory restrictions only respects single value restrictions

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

angela updated OAK-7982:
------------------------
    Attachment: OAK-7982.patch

> ACL.addEntry: check for mandatory restrictions only respects single value restrictions
> --------------------------------------------------------------------------------------
>
>                 Key: OAK-7982
>                 URL: https://issues.apache.org/jira/browse/OAK-7982
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, security
>            Reporter: angela
>            Assignee: angela
>            Priority: Major
>         Attachments: OAK-7982.patch
>
>
> The validation of {{ACL.addEntry(Principal principal, Privilege[] privileges, boolean isAllow, Map<String, Value> restrictions, Map<String, Value[]> mvRestrictions)}}
> includes a check that mandatory restrictions are actually present.
> However, the code performing that check only tests if the mandatory restrictions are included in the {{restrictions}} ignoring the fact that a mandatory restriction might be multi-valued and thus provided in the {{mvRestrictions}} param.
> cc: [~stillalex] fyi.



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