You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by shivalika <de...@gmail.com> on 2010/06/03 08:09:07 UTC
Authorization in JackRabbit
It have seen that Jackrabbit has no "native" Authorization provided with it.
>From "Authorization" i want that a logged in user has permissions to
read/write/remove a: Node and/or property or even rights to login to a
workspace.
Are people implementing it by themselves on AccessMAnager??
or they using JeCARS to implement repository Authorization??
or some other pre-built product?
what others are witnessing with Authorization & permissions in JackRabbit?
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Authorization-in-JackRabbit-tp2241239p2241239.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Authorization in JackRabbit
Posted by Justin Edelson <ju...@gmail.com>.
On Jun 3, 2010, at 1:17 PM, shivalika <de...@gmail.com> wrote:
>
> Thanx for sharing information about this.
>
> how can users be created using DAVExplorer in jackrabbit?
I'm not aware that they can be.
>
> Thank you & regards..
> --
> View this message in context: http://jackrabbit.510166.n4.nabble.com/Authorization-in-JackRabbit-tp2241239p2242024.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Authorization in JackRabbit
Posted by shivalika <de...@gmail.com>.
Thanx for sharing information about this.
how can users be created using DAVExplorer in jackrabbit?
Thank you & regards..
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Authorization-in-JackRabbit-tp2241239p2242024.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Authorization in JackRabbit
Posted by Justin Edelson <ju...@gmail.com>.
On 6/3/10 2:09 AM, shivalika wrote:
>
> It have seen that Jackrabbit has no "native" Authorization provided with it.
This is not the case.
>
> From "Authorization" i want that a logged in user has permissions to
> read/write/remove a: Node and/or property or even rights to login to a
> workspace.
By default, login rights to a workspace are implemented by granting read
access to the root node in the workspace. Note that JCR and Jackrabbit
do not support the notion of per-property access control. You can,
however, separate the ability to modify properties from the ability to
add and remove child nodes.
Justin
>
> Are people implementing it by themselves on AccessMAnager??
> or they using JeCARS to implement repository Authorization??
> or some other pre-built product?
>
> what others are witnessing with Authorization & permissions in JackRabbit?