[CalendarServer-dev] [CalendarServer] #260: OpenLDAP

CalendarServer trac at macosforge.org
Fri Jun 26 04:34:33 PDT 2009


#260: OpenLDAP
---------------------------------------+------------------------------------
 Reporter:  jusiskin@…                 |       Owner:  wsanchez@…        
     Type:  Feature                    |      Status:  new               
 Priority:  3: Important               |   Milestone:  CalendarServer-2.x
Component:  Calendar Server            |    Severity:  Other             
 Keywords:                             |  
---------------------------------------+------------------------------------

Comment(by oxullo@…):

 I'd like to add some lines about my personal experience trying to make
 OpenLDAP work with DCS.
 First of all, thanks to Aymeric and Brandon for their proposals.
 I tried both suggestions, with these objectives:

  * To integrate iCal and TB+Lightning 1.0pre in a calendar system, using
 an OpenLDAP directory to hold user's data
  * To have attendees' lookups work with both iCal and TB+L
  * To reduce the complexity of users' schema (quite naive implication, but
 relevant to the fact that there are no tools, at least known to me, to
 easily maintain directory's data)

 As reported in many forums
 ([http://discussions.apple.com/thread.jspa?messageID=9201124 1],
 [http://www.zimbra.com/forums/isync-caldav/14812-ical-attendee-lookup-
 using-zimbra-directory.html 2],
 [http://forums.kerio.com/index.php?t=msg&goto=51672 3],
 [http://discussions.apple.com/message.jspa?messageID=9469770 4]) iCal
 lookup troubles are caused by the lack of some information on which iCal
 rely, in order to set a proper scoping relating calendar server with
 server's users.

 1. Brandon Evans' package
   Finely documented installation process (wiki page here:
 [http://wiki.expertmx.com/doku.php?id=applecalendarserver 5]). This
 suggestion seems to be the most integrated solution for iCal's
 requirements.
   However, I could not make it work: no explicit errors, but calendars
 placeholders are not automatically generated on document root's structure,
 so I end up with principals with no default calendar. I can provide more
 details to whom is interested.
   Moreover, my concern is: whenever this solution works, how am I supposed
 to maintain it platform independently? Resource info, service locators et
 cetera..

 2. Aymeric Augustin's patch
   Completely undocumented, but quite straightforward and at least simple
 solution for RFC2307 integration. I could make it work (at least with no
 groups, nor delegates) but clearly no lookup support for iCal.
   In this specific situation I peeked into iCal<>LDAP communication.
 Lookup request is performed with the correct filter and data are returned,
 but iCal simply discard them. TB+L lookups are damned easy and they work
 out of the box.

 Relatively to iCal, it seems to me that the easiest way to fix this
 problem is to break the need of iCal to filter out contacts with high
 level metadata. Isn't possible just to configure this behavior?

 Another thing that shakes me is that lookup for local groups works
 [http://discussions.apple.com/message.jspa?messageID=9469770 4]. I don't
 really want to end up to maintain a fake group list on each company's Mac!

  1. http://discussions.apple.com/thread.jspa?messageID=9201124
  2. http://www.zimbra.com/forums/isync-caldav/14812-ical-attendee-lookup-
 using-zimbra-directory.html
  3. http://forums.kerio.com/index.php?t=msg&goto=51672
  4. http://discussions.apple.com/message.jspa?messageID=9469770
  5. http://wiki.expertmx.com/doku.php?id=applecalendarserver

-- 
Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:18>
CalendarServer </>
HTTP/WebDAV/CalDAV Server


More information about the calendarserver-dev mailing list