[Kolab-devel] [issue182] Decoupling the Kolab server object from fixed LDAP location

[Igor Genibel]

New submission from Igor Genibel <igor at genibel.org>:

This is a wish item from the eforum wishlist topic: 
 
At this stage the Kolab server is fixed as k=kolab under the base  
 DN.  
  
 Also users are fixed as inetOrgPerson under the base DN and  
 Address book entries under cn=external under the base DN.  
  
 I propose that a: The location of the Kolab server should be  
 configurable.  
  
 Any entry of the correct objectClass should be configurable as a  
 Kolab server. Perhaps kolab.conf file should contain the dn of the  
 Kolab server for that specific hierarchy.  
  
 Secondly. It should be configurable - either through the kolab.conf  
 file, or through LDAP - to add any arbitrary DN as a location for  
 users and addresses.  
  
 Possibly there could be a user_dn and address_dn attribute for  
 the Kolab object.  
  
 Example (in LDIF format):  
  
 dn: cn=mail-server1,dc=example,dc=com  
 objectClass: kolabServer  
 user_dn: ou=sales,dc=example,dc=com  
 user_dn: ou=admin,dc=example,dc=com  
 user_dn: ou=mktg,dc=example,dc=com  
 address_dn: ou=contacts,dc=example,dc=com  
 address_dn: ou=important,dc=example,dc=com  
  
 This Kolab server has 3 user ou's and 2 address ou's.  
  
 -Advantages?  
  
 Using this scheme several Kolab servers could exist within one  
 LDAP tree.  
 Organization wide directory replication can then be facilitated.  
 Changes/Updates are done on the Master OpenLDAP server and  
 then propogated throughout the organisation using slurpd  
 replication.

----------
assignedto: kolab-devel
messages: 587
nosy: igenibel, kolab-devel
priority: wish
status: unread
title: Decoupling the Kolab server object from fixed LDAP location
topic: server
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue182>
________________________________________________