Got it. Thanks. Now I can log in and browse to the users within / calendars, but not further down to the calendars I want to set the ACLs on. I'm thinking that my admin user isn't really an admin. I got the guid URL from the /principals/users/admin/ collection listing and pasted it in my caldavd.plist as follows: <key>AdminPrincipals</key> <array> <string>/principals/__uids__/XXX/</string> </array> restarted the server and I still can't drill down to calendars so I can set the ACLs on them. Something I'm missing on AdminPrincipals? Cheers, tack On Feb 16, 2008, at 5:12 AM, Stephen Bowman wrote:
New account of type CalDav, put in admin credentials, server hostname only, under the options section set the path as I described below. Then it should connect and you can browse the directory structure of DCS to get to the calendar you want to edit principals on.
The problem I was having was that I was using the wrong path. My current settings which seem to work fine are:
path = "/calendars/" login as admin...
Then edit the calendar for which you want to grant permission on. For example, to steal Cyrus' wording:
To give read read access on user02's calendar to user01:
If you really want to use ACLs, then set the ACLs on /calendars/users/user02/calendar to give /principals/__uids__/XXX (whatever the principalURL is for user01) read access.
It worked for me...