This content has been marked as final. Show 4 replies
I need a little more information:
1) Support for read-free-busy
How are you trying to set this?
Free-busy rights are set on a user's account, not on their individual calendars. You should see the free-busy rights for a user when you use the get_accountprops wcap command.
2) ACL should reflect the rights for all users
How are you getting the ACL, via get_calprops wcap? If so, this will only show you the r/w rights to the calendar, not the free-busy rights.
For the 1), you're right, i think i misread the description.
For the 2), if you're the owner of a calendar, say /dav/home/user1@domain/Parties/
If this Calendar is granting read to everyone + read-write for a specific user, you can run this:
URI : /dav/home/user1@domain/Parties/
<?xml version="1.0" encoding="utf-8"?>
You should get the acl, but no ace entry for "D:authenticated" or "D:all" in it...do you ?
Something like this :
<!-- etc. with write-properties, write-content, unbind, bind -->
<D:status>HTTP/1.1 200 OK</D:status>
I'm assuming that you are using only WebDAV ACL + CalDAV to get/set the acls.
The trouble is that the WebDAV ACL specification is so flexible in the way that ACLs can be represented that so far not many clients are really making use of it, and when they are, it is in a different manner. As a consequence, you will find most server implementations incomplete at best.
Now as far as your particular issues, they seem reasonable to fix.
About the first one, we are talking about the privilege that is applied on the scheduling inbox, as defined in http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-10#section-220.127.116.11 right ?
Are you in a position to file two SR describing the exact commands that you are trying to send with their expected result so that they get fix for sure in update3 ?
If you need a temporary workaround, you can use the wcapbis protocol for this type of operation.
See https://wikis.oracle.com/display/CommSuite/set_calprops.wcap for setting read access and https://wikis.oracle.com/display/CommSuite/set_accountprops.wcap for setting freebusy access.
One undocumented feature is that you can use pretty much the same url that you are using for caldav also for wcapbis, just changing dav prefix with a wcap prefix and appending the wcap command at the end of the uri.
For example, if your original relative calendar uri looks like:
you can use a uri like
to get back the calendar properties of the calendar (i.e. no need for the calid or id parameters).
Thank both of you for these hints.
I'm using WebDAV and CALDAV, yes, i'd prefer to avoid specific code if i can, but if there's no other choice i'll have a look at wcap methods.
Here is the unfinished module, in order to have an idea of what i get from the server.
Please keep in mind that it is not fully functional...