[Opensync-commits] r5330 - plugins/ldap-sync

[<svn...@op...>]

Author: scriptor
Date: Thu Mar 26 01:11:56 2009
New Revision: 5330
URL: http://www.opensync.org/changeset/5330

Log:
Initial version of the LDAP plugin having been ported to libopensync-0.3x.

Added:
   plugins/ldap-sync/NEWS   (contents, props changed)

Added: plugins/ldap-sync/NEWS
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ plugins/ldap-sync/NEWS	Thu Mar 26 01:11:56 2009	(r5330)
@@ -0,0 +1,54 @@
+$Id$
+
+
+March 2009:
+
+The ldap plugin has been ported to openldap-2.4 and opensync-0.39 (r5291).
+The plugin has been splitted up in the actual ldap-sync plugin
+and the ldap-format plugin.
+
+All 4 object types can be synchronized.
+
+The mapping from
+
+xmlformat-contact,
+xmlformat-event,
+xmlformat-todo,
+xmlformat-note
+
+to
+
+ldap-evolutionperson or ldap-inetorgperson,
+ldap-event,
+ldap-todo,
+ldap-note
+
+and vice versa is NOT loss-free and by far not bug-free, yet.
+
+The mapping is performed in two steps:
+
+1. From xmlformat-contact, for example, to some ldap-plugin
+   internal XML format.
+
+2. From this internal XML format to C structs suitable for libldap.
+
+And vice versa.
+
+Some fields are not mapped, at all.
+
+Some other fields are mapped to some subentry of objectClass 
+"organizationalUnit" instead of being mapped to objectClass 
+"evolutionperson".  This is a workaround for the problem that
+the formats used by libopensync are not really compatible
+to the various LDAP schemes generally used.
+
+There is still no support for XML elements that occur MORE than
+one time, like two or three addresses.
+
+And there is no real support for deeper XML element levels, either,
+as it can be found in the "<Address>"-element.
+
+For other changes see ChangeLog.
+
+
+