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

[Torsten Grote]

Hi Erik,

this is almost something for the development list. I remember, that Timotheus 
(CCed) was working on automating the addition of new domains even more, but I 
don't know what his efforts have led to.

Kind Regards,
Torsten

On Saturday 21 September 2013 11:12:08 Erik M Jacobs wrote:
> Hi all,
> 
> Looking at these docs:
> http://docs.kolab.org/en-US/Kolab_Groupware/3.0/html-single/Administrator_Gu
> ide/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?

-- 
Torsten Grote, Kolab Evangelist

Kolab Systems AG, Zürich, Switzerland

e: grote at kolabsys.com
t: +41 43 501 66 91
w: http://kolabsys.com

pgp: 274D 4F97 Torsten Grote
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20130923/81f3f8d4/attachment.sig>