[CalendarServer] #307: Minor doc nit with major implications: iCal client requires a Directory to allow sharing
#307: Minor doc nit with major implications: iCal client requires a Directory to allow sharing -----------------------------+---------------------------------------------- Reporter: ggm@apnic.net | Owner: wsanchez@apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | -----------------------------+---------------------------------------------- I may be wrong, but from my test it looks like you cannot make iCal client do an Account->Access->[Edit] and the [+] add a person unless you have a Directory source bound, which can map the names to __uuid__ values. If you *know* the __uuid__ then all is well. But, most people know LDAP identity information. I think it might help to document this here, in the sharing guides, so its clear you have to configure it. Typically, this is done by running the 'Directory Utility' to add an LDAPv3 server, or an Apple Directory. I believe you also have to stop/start the iCal client to have this update honoured. -George -- Ticket URL: <http://trac.calendarserver.org/ticket/307> CalendarServer </> HTTP/WebDAV/CalDAV Server
#307: Minor doc nit with major implications: iCal client requires a Directory to allow sharing --------------------------------+------------------------------------------- Reporter: ggm@… | Owner: wsanchez@… Type: Defect | Status: closed Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Resolution: Behaves correctly | Keywords: --------------------------------+------------------------------------------- Changes (by wsanchez@…): * status: new => closed * resolution: => Behaves correctly Comment: This is a limitation in iCal, which relies on Directory Services for the information is feeds into that panel. That can't be fixed by the server, so tracking that here, isn't useful. We've recently added a new `REPORT` which should allow clients to do principal queries against the CalDAV server, so that the client doesn't have to be bound to the same directory system as the server (which isn't necessarily possible, eg. with a file-based directory). -- Ticket URL: <http://trac.calendarserver.org/ticket/307#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server
participants (1)
-
CalendarServer