jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Gomez" <sage...@gmail.com>
Subject Re: Jackrabbit 1.5 ACL Basics
Date Thu, 08 Jan 2009 11:20:43 GMT
Hi again.
I found the builtin_nodetypes.xml file in the
org.apache.jackrabbit.core.nodetype package that has helped me understand
what the hierarchy must look like. I've concluded any node can be access
controlled by assigning it the "rep:AccessControllable" mixin type, giving
it a child node of primary type "rep:ACL" and this last one must have one
child node of primary type "rep:ACE" for each entry in the list. If it's not
too much asking, I'd appreciate anyone having a good understanding on this
area to confirm my conclusion.


Sebastian Gomez.

On Wed, Jan 7, 2009 at 6:35 PM, Sebastian Gomez <sage.es@gmail.com> wrote:

> Hi everyone.
> I'm trying to find some documentation on Jackrabbit 1.5 security using
> ACLs, and I haven't found very much so I hope someone can help me out with
> this. I'm trying to initialize my repository creating the ACL and ACE nodes
> by hand, without having to do it programatically. I'd like to know what kind
> of structure I should use. Looking at the source code I've come to the
> conclusion that my access controlled nodes must have the mixin type rep:acl,
> and a child node with mixin type rep:ace for each entry. These entries will
> then have the principal and privileges in it's properties, that must have
> the name specified in the AccessControlConstants interface. Is this the
> basic idea or am I being mistaken?
> Thanks in advance.
> Sebastian Gomez.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message