You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Andreas Probst <an...@gmx.net> on 2002/09/19 17:51:46 UTC

Users, Roles, Groups, ACL

Hi Slide users and developers,

after testing (or rather trying) with Slide 1.0.16 and Slide 2 
(manually built on Aug 30) I observed the following behaviour:

Users need access permissions for the whole path, i.e. if john 
(or groupA) hasn't access to / he won't have access to /files, 
although I grant /actions to +/users/groupA on /files.

I would like to have the following behaviour: 
- / can only be accessed by /users/root
- /files/groupDirA can be accessed by +/users/groupA
- /files/groupDirB can be accessed by +/users/groupB

Maybe I would like to have even deeper hierarchies, where in 
deeper directories more or different people are allowed to 
access. 

How can this be achieved with Slide?

Is it possible to set permissions based on roles AND groups?
So I would like to grant read permission on /files/groupDirA to 
each member of groupA, but write permission only to users having 
a writer role AND belonging to the groupA.

Can this be done in Slide?

I hope so, otherwise it will become very, very difficult I 
suppose. So I would really appreciate answers and hints on how 
to achieve such a behaviour.

Thanks in advance.

Andreas 

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Users, Roles, Groups, ACL

Posted by Andreas Probst <an...@gmx.net>.
Hi Sliders,

I found part of a solution for the problem described below.

I don't differentiate roles, but make sub groups. So it's 
possible, that users are writers in one group and readers only 
in another group.
 
/users/groupA/readers, /users/groupA/writers and
/users/groupB/readers, /users/groupB/writers.

Then I grant the following permissions to /files/groupDirA:
+/users/groupA/readers /actions/read and
+/users/groupA/writers /actions/write 

and similar to /files/groupDirB.

Of course on / and /files there must be 
/users 		/actions/read 		not inheritable

Webfolders and Slide client won't even show the existence of 
other group directories. I think I will make sure my own 
WebdavServlet also doesn't do it.

But unfortunately there is still a problem regarding versioning. 
If I want to give the users the possibility to read old 
versions, I have to give read permission on /history. But then 
they can also read the history files of other groups. I think 
this could be solved by setting the read permissions after 
creation of versions. But what about the writers? I have to give 
them write permission, but that enables them to write directly 
into the /history directory. I don't have an idea, how to solve 
this.

Do you have an idea or solution how to block writing into 
/history but at the same time enabling versioning? Any pointers 
or hints would be really appreciated.

Andreas


> Hi Slide users and developers,
> 
> after testing (or rather trying) with Slide 1.0.16 and Slide 2 
> (manually built on Aug 30) I observed the following behaviour:
> 
> Users need access permissions for the whole path, i.e. if john 
> (or groupA) hasn't access to / he won't have access to /files, 
> although I grant /actions to +/users/groupA on /files.
> 
> I would like to have the following behaviour: 
> - / can only be accessed by /users/root
> - /files/groupDirA can be accessed by +/users/groupA
> - /files/groupDirB can be accessed by +/users/groupB
> 
> Maybe I would like to have even deeper hierarchies, where in 
> deeper directories more or different people are allowed to 
> access. 
> 
> How can this be achieved with Slide?
> 
> Is it possible to set permissions based on roles AND groups?
> So I would like to grant read permission on /files/groupDirA to 
> each member of groupA, but write permission only to users having 
> a writer role AND belonging to the groupA.
> 
> Can this be done in Slide?
> 
> I hope so, otherwise it will become very, very difficult I 
> suppose. So I would really appreciate answers and hints on how 
> to achieve such a behaviour.
> 
> Thanks in advance.
> 
> Andreas 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>