Hi

I added a docu page about the jackrabbit-accessmanager bundle under
[1]. Please let me know if something is incorrect or missing.

[1] 
http://cwiki.apache.org/confluence/display/SLINGxSITE/Managing+permissions+(jackrabbit.accessmanager)

best regards
mike


> -----Original Message-----
> From: Francisco Jesús González Mata [mailto:[email protected]]
> Sent: Tuesday, September 01, 2009 9:01 PM
> To: [email protected]
> Subject: Re: UserManager, Authorization and Authentication
>
>
> Thanks to Eric Norman to solve the immediate problem and
> Vidar Ramdal to
> clarify where I must use LDAP authentication.
> Thanks a lot.
>
> Regards, F.J. Gonzalez
>
> 2009/9/1 Vidar Ramdal <[email protected]>
>
> > 2009/8/31 Francisco Jesús González Mata <[email protected]>:
> >
> > > How can I assign permissions to an user? Is there any API like
> > userManager
> > > for this matter? Could anybody give me an example?
> >
> > > As alternative, I have read that AccesManager manages
> Authorization and
> > > LoginModule Authentication, and that by implementing my
> own accesmanager
> > I
> > > could even use other authorizable mechanism like LDAP. Am
> I in the right
> > > way? I have tried to implement my own AccessManager in
> Jackrabbit-core
> > 1.5,
> > > but I must be doing anything wrong. Or should I wait for
> Jackrabbit 2.0
> > or
> > > for more documentation?
> >
> > But as you say, AccessManager is for Authorization and
> LoginModule for
> > Authentication. The LoginModule issues Principals for a user when he
> > logs on. The AccessManager decides if a Principal is allowed to do a
> > specific action, but doesn't care where the Principals originated.
> >
> > LDAP only holds user info, not repository access rights. So throwing
> > LDAP into the mix will not save you from setting access rights - you
> > will still need to interact with the AccessManager in some way.
> >
> > --
> > Vidar S. Ramdal <[email protected]> - http://www.idium.no
> > Sommerrogata 13-15, N-0255 Oslo, Norway
> > + 47 22 00 84 00 / +47 21 531941, ext 2070
> >
>

Reply via email to