new domains without changes to /etc/kolab/kolab.conf OR "pure" LDAP-only administration

[Erik M Jacobs]

I am reviving this very old thread.

At one point some of the changes required to do this were available in
updates/testing repositories.  Did these changes officially make it into
3.1 (or whatever the latest stable release is)?

Erik M Jacobs
Director, JumpShip Services
A Division of EjectButton, Ltd
PGP Key ID: 9CA64161

On 09/21/2013 11:12 AM, Erik M Jacobs wrote:
> Hi all,
> 
> Looking at these docs:
> http://docs.kolab.org/en-US/Kolab_Groupware/3.0/html-single/Administrator_Guide/index.html#sect-Administrator_Guide-Adding_Domains-Adding_a_New_Domain
> 
> Specifically referring to #6:
> "The new domain has now been created in LDAP. For the web administration
> panel to pick up on various settings related to the new domain name
> space, edit /etc/kolab/kolab.conf and at a very minimum, add a new
> section for the new domain and set the base_dn setting."
> 
> We're very interested in automation, and editing config files is a bit
> of a bear.  Since most of what the admin interface does is update LDAP,
> if we're not "using" the admin interface to add/modify/etc., we wouldn't
> need to update the kolab config file, would we?
> 
> In other words -- whatever Kolab's admin interface does to add new
> domains on the back-end, as long as we do the same thing in LDAP, we
> should be fine, right?
>