I have Slide webdav server 2.1 M1 installed on my Windows 2000 box. I run it as 
a webapp under Tomcat 5.0. I am using Webdav client 2.1 M1 to test the role 
based permission features. When I grant permissions using the "grant" command 
to a resource, and use the "acl" command to look the granted permissions, I 
find that every added permission has a prefix of "nc3". Lets say you are 
granting a write persmission using the following command:
grant write on /Slide/files/rootdir4 to /Slide/users/john
Permission gets granted successfully. When you use following acl command:
acl /Slide/files/rootdir4, you see the following:
ACL for /Slide/files/rootdir4:
------------------------------------------------------------
granted to /Slide/users/john    (not protected)   (not inherited)
   DAV:nc3write
granted to /Slide/users/user1    (not protected)   (inherited 
from '/Slide/files')
   DAV:all
granted to /Slide/roles/user    (not protected)   (inherited 
from '/Slide/files')
   DAV:write
granted to property    (not protected)   (inherited from '/Slide/files')
   DAV:read-acl
granted to /Slide/roles/root    (not protected)   (inherited from '/Slide/')
   DAV:all
granted to all    (not protected)   (inherited from '/Slide/')
   DAV:read
------------------------------------------------------------

Note the prefix "nc3" for the write persmission granted.

Also, on the Slide server console, you will see the following warning::
09 Aug 2004 10:12:49 - org.apache.slide.security.SecurityImpl - WARNING - Unknow
n action /actions/nc3write

After assigning this permission, you will find that the permission is not valid 
anymore, I mean user john cannot write to the resource "/Slide/files/rootdir5".

I am in a project where we are building a UI for granting permissions in Slide. 
We are stuck at this point with this bug. If I point my Java module to Webdav 
client 2.0 library, everything works fine. Or, If I use webdav client 2.0 
command line tool, everything works fine. I thing the bug was generated in 
2.1M1. Unfortunately 2.1M1 has other bug fixes that I use, so cannot go back to 
2.0. 

thanks,
Krishna