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

CalendarServer trac at macosforge.org
Thu Nov 27 09:23:05 PST 2008


#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 aymeric.augustin@…):

 I've been developping a solution to plug calendarserver into a standard
 OpenLDAP installation under Debian for a few days. My goal is to have a
 module that works on *your* setup without any tuning apart from the
 configuration in caldavd.plist. I'm doing it because I couldn't figure out
 how Brandon's solution is working or what his schema is.

 The main problem I've been tackling is: how to provide a flexible way to
 interpret the LDAP data as records of different types? For example, there
 are several ways to implement groups. I've designed a solution to specify
 all this data in caldavd.plist, assuming the most standard schemas are
 used. Basically, for each record type, I give the base DN and the name of
 the attribute for the RDN. Then there's quite a lot of glue code to
 implement the interface.

 I'm attaching a diff file with my current implementation. It's a work in
 progress and I'm aware that several things need fixing, especially replace
 hardcoded stuff by configuration, implement the "proxy" stuff, and avoid
 synchonous operations (I do not really need caching at this time). I would
 really appreciate comments on my approach:
 - is the configuration understandable (see the changes in config.py)?
 - would that work with your LDAP setup?

 If there is positive feedback, I'm willing to improve the code so that it
 can be integrated in calendarserver.
 Otherwise, maybe that will help with the "design issues" mentionned here:
 http://lists.macosforge.org/pipermail/calendarserver-
 users/2007-May/000304.html

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


More information about the calendarserver-dev mailing list