Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of anchela@day.com designates
 207.126.148.183 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <22287762.post@talk.nabble.com>
References: <22287762.post@talk.nabble.com>
Date: Mon, 2 Mar 2009 16:09:09 +0100
Message-ID: <bfeaddf70903020709v11b92b74lf6e4e5ca71c8df35@mail.gmail.com>
Subject: Re: WebDAV and ACLs
From: Angela Schreiber <anchela@day.com>
To: users@jackrabbit.apache.org
Content-Type: multipart/alternative; boundary=000e0cd250aa5218340464243353

--000e0cd250aa5218340464243353
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

hi marian

i would go for #2.
the ACL api you are referring to will be part of jsr 283 which is
not yet completed nor final. a snapshot of the interfaces has
been copied to jackrabbit-api/o.a.j.api.jsr283.security.

principal management on the other hand is out of the scope
of jsr 283. that's why it is defined in jackrabbit-api/o.a.j.api.security.

for documentation please read the latest public review of jsr 283.
there is not other further documentation available.

for the principal-management LDAP story you need to write
a custom PrincipalProvider or - alternatively - some tool that
synchronizes the repository users with your LDAP.

please note, that the security API with jackrabbit is still work
in progress.

angela


--
View this message in context:
http://www.nabble.com/WebDAV-and-ACLs-tp22287762p22287762.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

--000e0cd250aa5218340464243353--