Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of sriramnrn@gmail.com designates
 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=o1LZMU4qI7szTc1zz9VvVCdJIkIR1wsiJ//OdVuwg2r/+DHokRoG+iU5ZIefCnfe8Rz0Fl64wErn3ReZkGuiIGGPHEModQSNgW8+KZc5VMrUt214bAwhbxdMSxq2QhtqVhgO2xIdNWLVumGxibTWBdtf+bV6OEIp+J+M/pLe86Q=
Message-ID: <49977f270702021001mafbb1b7ic07815c6c11d4548@mail.gmail.com>
Date: Fri, 2 Feb 2007 23:31:38 +0530
From: "Sriram Narayanan" <sriramnrn@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: permissions on jcr nodes
In-Reply-To: <45C2F6B8.7000703@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <45C2F6B8.7000703@sun.com>

On 2/2/07, ruchi goel <Ruchi.Goel@sun.com> wrote:
> Hi all,
>   I want to know how r/w/o  permissions are used for jcr nodes. Session
> class is supposed to implement checkPermissions. Does Jackrabbit
> implement it ? As far as I can understand, It creates an instance of
> AccessManager . Does it allow plugging in the AccessManager ? Do we
> store permissions as properties of nodes ?
>
Yes. JackRabbit does indeed allow us to plug in our own access
managers. All you need to do is specify your class in the
repository.xml file. Read the sources for SimpleAccessManager and
you'll find some starting information for your own access manager.

Also, search the threads for the duration of October-November 2006,
and you'll find some posts by me and responses on how to write custom
Access Managers. I was supposed to complete my own implementation and
contribute that as a patch, but I'm really tied up with other work
right now.

Essentially, here's what you need to do:
1. Write your own EventListener.
2. Listen to Node creation and Node Deletion events via this EventListener.
3. Store the UUID and permission information of that node somewhere.
This has to be a location outside of your repository
4. When a Node is being accessed, you AccessManager should use the
UUID, look this up  in its own storage (mentioned in point 3 above),
and then return permissions for read and write as required.

-- Sriram