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 "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/08/18 12:06:02 UTC

[jira] [Updated] (OAK-6563) Session.hasCapability(...) should reflect read-only status of mounts

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

Robert Munteanu updated OAK-6563:
---------------------------------
    Summary: Session.hasCapability(...) should reflect read-only status of mounts  (was: CLONE - Session.hasCapability(...) should reflect read-only status of mounts)

> Session.hasCapability(...) should reflect read-only status of mounts
> --------------------------------------------------------------------
>
>                 Key: OAK-6563
>                 URL: https://issues.apache.org/jira/browse/OAK-6563
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: composite, security
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: 1.8, 1.7.6
>
>
> When a mount is set in read-only mode callers that check {{Session.hasPermission("set_property", ...)}} or {{Session.hasPermission("add_node", ...)}} for mounted paths will believe that they are able to write under those paths. For a composite setup with a read-only mount this should (IMO) reflect that callers are not able to write, taking into account the mount information on top of the ACEs.
> [~anchela], [~stillalex] - WDYT?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)