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 aklimets@day.com designates
 207.126.148.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <AEC5DC5C-65F3-4A38-836E-77AEC6F27123@gmail.com>
References: <AEC5DC5C-65F3-4A38-836E-77AEC6F27123@gmail.com>
Date: Tue, 3 Feb 2009 19:33:00 +0100
Message-ID: <c3ac3bad0902031033v1317089cl6a0c92a445da394b@mail.gmail.com>
Subject: Re: Permissions in JackRabbit 1.5
From: Alexander Klimetschek <aklimets@day.com>
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 30, 2009 at 5:08 PM, Miros=B3aw Ochodek
<miroslaw.ochodek@gmail.com> wrote:
> Could you please give me a reference to materials about permissions
> management in JR 1.5 (something more comprehensible than what is in
> configuraiton section on page).

There is not much documentation yet. A starting point is the original
issue [1]. If you plan to write your custom authorization, you should
also search the users and dev mailing lists, eg. at
http://jackrabbit.markmail.org

> I have seen that there is yet another interface - SecurityManager. I know
> that authorization should be handled externally with the use of own
> implamation of AccessManager and LoginManager.

Starting with JR 1.5, the default implementation is based on storing
users and ACLs in the repository, so there is no need to implement
your own classes for that purpose (except if you want to do it
differently). Citing JCR-1171:

    Default Implementation
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    The Default Implementation uses the Repository itself to store its
security data.
    The Users are stored within a dedicated workspace.
    The ACL are attached to the Nodes they relate to.
    The ACLs are inherited along the Item-Hierarchy.
    The Principals are taken from the Authorables.

> My question is what SecurityManager is for?

The security manager technically manages the auhtorization part of the
security implementation, ie. the AccessManager, PrincipleManager and
UserManager, it's not directly mapped to functionality (I hope I got
it right ;-)). See the interface for that class [2]. There are two
implementations, the DefaultSecurityManager [3] (the default impl
mentioned above) and the SimpleSecurityManager [4].


[1] http://issues.apache.org/jira/browse/JCR-1171

[2] http://svn.apache.org/repos/asf/jackrabbit/tags/1.5.0/jackrabbit-core/s=
rc/main/java/org/apache/jackrabbit/core/security/JackrabbitSecurityManager.=
java

[3] http://svn.apache.org/repos/asf/jackrabbit/tags/1.5.0/jackrabbit-core/s=
rc/main/java/org/apache/jackrabbit/core/DefaultSecurityManager.java

[4] http://svn.apache.org/repos/asf/jackrabbit/tags/1.5.0/jackrabbit-core/s=
rc/main/java/org/apache/jackrabbit/core/security/simple/SimpleSecurityManag=
er.java

Regards,
Alex

--=20
Alexander Klimetschek
alexander.klimetschek@day.com