Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 19 Jul 2012 06:49:33 +0000 (UTC)
From: "angela (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: <1128543291.74653.1342680574477.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <721440085.18174.1334251998432.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OAK-64) Privilege Management
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OAK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418117#comment-13418117 ] 

angela commented on OAK-64:
---------------------------

one more thing that isn't documented with your half way fix: the jcr:all privilege must
include all privileges (including custom)... that requirement of the spec is violated
right now and there is not TODO for that since it was obvious IMO.

and a final question: what does the client (i assume it's CQ) do with a custom privilege 
if access control is not implemented altogether? i would suggest that the client should 
deal with failing privilege registration instead of adding hacks to oak. 
                
> Privilege Management
> --------------------
>
>                 Key: OAK-64
>                 URL: https://issues.apache.org/jira/browse/OAK-64
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, jcr
>            Reporter: angela
>            Assignee: angela
>
> implement privilege management such as defined by jackrabbit API

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira