Well, this is strange. Any chance you can upgrade to 2.1b1? There have been a few fixes that *may* apply to this. I don't recognize the problem you're having, though, so no guarantees.

About the parent directory, user1 will need read access to any parent directories to have access to a child directory. Other than that, the permissions on the current directory override the permissions on the parents, so local write permissions should be sufficient.

-James

Hu Yong wrote:

The detailed description:


1) What version of the client library?

A: 2.1M1


2a) What version of Slide?

A: 2.1M1


2b) Are you using the Tomcat bundle, the webapp distribution, or did you
 compile you're own?

A: No, i don't use Tomcat bundle, but the built bin package.


3) Can user1 get a directory listing for sub1, or any other collection?
What rights *does* user1 have.

A: Yes, user1 can get the direcotry listing for sub1, furthermore, user can get sub1's ACL. I have grant user1 with all actions on sub1, including write,write-content,write-properties,read,read-acl ...

In addition, I found that if I grant sub1's parent directory files with
related actions(the inheritable is true), user1 can have whole access to
sub1. Does sub1's access permission depend on its parent directory though it
has itsself permission?


regards Huyong


----- Original Message ----- From: "James Mason" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, August 11, 2004 2:13 PM Subject: Re: A question about permission in slide(From YongHu)



Some questions:

1) What version of the client library?

2a) What version of Slide?

2b) Are you using the Tomcat bundle, the webapp distribution, or did you
 compile you're own?

3) Can user1 get a directory listing for sub1, or any other collection?
What rights *does* user1 have.

-James

Hu Yong wrote:

All,

I use webdav client lib to implement the permission management in slide,

and use command line provided with client lib to do some test.

The initial directory structure looks like following:

/
  -- files

rootuser has the whole control to all resource, and user1 has no any

permission initially.

I create a folder named sub1 under files using rootuser, and grant

read,read-acl,write,write-acl,write-content actions on sub1 to user1.(Note: I don't grant any actions to user1 on files folder). Then i can use cd files/sub1 to enter the sub1 folder, and use acl to display the user1's permission.

/
 --files
      -- sub1

However, when I use 'mkcol sub2' under sub1, the Forbidden (403) error

is thrown. I don't know why the mkcol is forbidden since the write action has been granted to user1.

(the permission definition in  sub1.def.xml is

  <permissions>
 <permission subjectUri="/users/user1" actionUri="/actions/read"

inheritable="true" negative="false" />

<permission subjectUri="/users/user1" actionUri="/actions/write"

inheritable="true" negative="false" />

 </permissions>


Could anyone give me some suggestion?

thanks in advance.

regards
huyong



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to