to maintain kolab LDAP data (inetOrgPerson only) as horde ad

Thu, 18 Sep 2008 14:26:26 +0000

to maintain kolab LDAP data (inetOrgPerson only) as horde admin through horde i added my manager dn + pw to horde's conf.xml and accessed this through a modified kolab_global source in turba's sources.php. conf.xml patch is attached, my kolab_global source definition is below: /* Only use LDAP if we have that extension in PHP */ if (function_exists('ldap_connect')) { require_once 'Horde/Kolab.php'; if (!is_callable('Kolab', 'getServer')) { $_kolab_server = $GLOBALS['conf']['kolab']['ldap']['server']; } else { $_kolab_server = Kolab::getServer('ldap'); } /* A global address book for a Kolab Server. This is typically a * read-only public directory, stored in the default Kolab LDAP server. * The user accessing this should have read permissions to the shared * directory in LDAP. */ if ( Auth::isAdmin() ) { $_bind_dn = $GLOBALS['conf']['kolab']['ldap']['binddn']; $_bind_pw = $GLOBALS['conf']['kolab']['ldap']['bindpw']; } else { $_bind_dn = $GLOBALS['conf']['kolab']['ldap']['phpdn']; $_bind_pw = $GLOBALS['conf']['kolab']['ldap']['phppw']; } $cfgSources['kolab_global'] = array( 'title' => _("Global Address Book"), 'type' => 'ldap', 'params' => array( 'server' => $_kolab_server, 'port' => $GLOBALS['conf']['kolab']['ldap']['port'], 'tls' => false, 'root' => $GLOBALS['conf']['kolab']['ldap']['basedn'], 'sizelimit' => 200, 'dn' => array('cn'), 'objectclass' => array( 'top', 'inetOrgPerson', 'kolabInetOrgPerson', ), 'filter' => 'objectClass=kolabInetOrgPerson', 'scope' => 'sub', 'charset' => 'utf-8', 'version' => 3, 'bind_dn' => $_bind_dn, 'bind_password' => $_bind_pw, ), 'map' => array( '__key' => 'dn', 'name' => 'cn', 'firstname' => 'givenName', 'lastname' => 'sn', 'email' => 'mail', 'alias' => 'alias', 'title' => 'title', 'company' => 'o', 'workStreet' => 'street', 'workCity' => 'l', 'workProvince' => 'st', 'workPostalCode' => 'postalCode', 'workCountry' => 'c', 'homePhone' => 'homePhone', 'workPhone' => 'telephoneNumber', 'cellPhone' => 'mobile', 'fax' => 'fax', 'notes' => 'description', 'freebusyUrl' => 'kolabHomeServer', ), 'search' => array( 'name', 'firstname', 'lastname', 'email', 'title', 'company', 'workAddress', 'workCity', 'workProvince', 'workPostalCode', 'workCountry', 'homePhone', 'workPhone', 'cellPhone', 'fax', 'notes', ), 'strict' => array( 'dn', ), 'export' => true, 'browse' => true, ); }

Turba is an address book, not a user manager. Kolab will not

Fri, 07 Nov 2008 13:44:28 +0000

Turba is an address book, not a user manager. Kolab will not mix these two aspects and any user management features need to be added to the Horde admin menu. If you followed CVS you will have noticed that the Kolab_Server module as well as the Kolab driver in the Auth module got extended for managing Kolab users. There is currently no frontend for that but this will probably be created next year. If you have some time to invest into this it should not be too hard to write the pages in the Horde admin section required for Kolab user management. Marking as "stalled" for now as I'm not going to work on this during the next months.

I guess this can be resolved now that there is koward?

Tue, 18 Aug 2009 22:37:45 +0000

I guess this can be resolved now that there is koward?

horde as kolab-webadmin

to maintain kolab LDAP data (inetOrgPerson only) as horde ad

Turba is an address book, not a user manager. Kolab will not

I guess this can be resolved now that there is koward?