#260: OpenLDAP
---------------------------------------+------------------------------------
Reporter: jusis...@… | Owner: wsanc...@…
Type: Feature | Status: new
Priority: 3: Important | Milestone: CalendarServer-2.x
Component: Calendar Server | Severity: Other
Keywords: |
---------------------------------------+------------------------------------
Comment(by aymeric.augus...@…):
You're right about the lack of documentation of my patch. Non-obvious
configuration options should be documented, at least.
Groups are supported "flexibly". Here is how.
* If you don't use NIS groups, group records have member fields giving
the dn of each user belonging to the group. This is the default
configuration :
{{{
<key>groupSchema</key>
<!-- Base LDAP groups -->
<dict>
<key>membersAttr</key>
<string>member</string>
<key>memberIdAttr</key>
<string></string>
</dict>
}}}
* If you use NIS groups, group records have memberUid fields giving the
uid of each user belonging the group. The dn of the user can be rebuilt
with the information in the rdnSchema section of the configuration.
{{{
<key>groupSchema</key>
<!-- NIS groups -->
<dict>
<key>membersAttr</key>
<string>memberUid</string>
<key>memberIdAttr</key>
<string>uid</string>
</dict>
}}}
* Other representations could probably be mapped to one of these two.
Delegates are not supported, I'm not even sure what they are.
The configuration may be too generic and too flexible. However the
defaults work out of the box. Do you have an opinion on this matter?
--
Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:19>
CalendarServer </>
HTTP/WebDAV/CalDAV Server
_______________________________________________
calendarserver-dev mailing list
calendarserver-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-dev
