You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2011/05/26 23:47:47 UTC

[jira] [Updated] (JCR-2977) AccessControlManager#getApplicablePolicy should check for colliding rep:policy node

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

angela updated JCR-2977:
------------------------

      Component/s: security
                   jackrabbit-core
    Fix Version/s: 2.3.0

> AccessControlManager#getApplicablePolicy should check for colliding rep:policy node
> -----------------------------------------------------------------------------------
>
>                 Key: JCR-2977
>                 URL: https://issues.apache.org/jira/browse/JCR-2977
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, security
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.3.0
>
>
> while AccessControlManager#getApplicablePolicy returns an empty iterator if the target node cannot get the accesscontrollable-mixin set, it does not test if there is a colliding child node that would prevent the policy to be applied calling AccessControlManager#setPolicy. consequently, the setPolicy call fails with ItemExistsException. A simple test upfront could prevent this unexpected failure.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira