[Kolab-devel] Administration of the Horde configuration

[Gunnar Wrobel]

Hi!

Currently the way the Horde configuration is handled on the Kolab
server is still somewhat problematic (see also
http://kolab.org/pipermail/kolab-devel/2007-December/008210.html).

Parts of the configuration (the kolab.php files in horde/config and
horde/kronolith/config) use the Horde template mechanism and will
always overwrite the settings done with the Horde administration
frontend. This currently still lacks explanation.

In addition you currently get the administration frontend if you log
in as "manager" into Horde. This type of login is possible but partly
broken because the manager account is a special IMAP account.

I think the best way to deal with horde configuration is to fully
disallow login as a non-standard IMAP user and thus fully disable
Horde configuration by default.

This could then be activated by adding a specific user within
horde/config/conf.php as Horde administrator. This user could then
modify the Horde configuration but should be aware that a very small
set of values cannot be set. We could either add an explanation on the
wiki or add it to README.1st.

Comments, other ideas?

Thanks!

Gunnar


-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~