Autconfiguration for kolabclient

Christian Mollekopf mollekopf at
Fri Jun 20 14:30:35 CEST 2014

On Wednesday 04 June 2014 13.23:22 Aleksander Machniak wrote:
> On 06/04/2014 11:56 AM, Sandro Knauß wrote:
> > for beeing able to auto configure the client, we should create a file at
> > the server to get most settings for the client. As base I used the
> > Thunderbird autoconfig file [1].
> > 
> > I added additional xml tags for ldapserver, freebusy and identities.
> Some notes to consider:
> - all these sections should be put inside emailProvider.
Why? IMO it makes sense to have the separately.

> - maybe instead of <ldapServer id="..."> we should do <addressbook
> type="ldap" id="...">?
I suppose whether we setup an ldap service (for whatever use), or whether we 
setup addressbooks. If you think of resourcemanagement etc. it IMO makes sense 
to setup the ldapServer, and not an addressbook.

> - in Roundcube identities can be in HTML format
In Kontact as well, so if we include that HTML should be supported.

> > Different modes:
> > * requesting the file with auth basic  -> fill out password etc.
> > * without login data -> return the file with %PASSWORD%, %USER%,...
> > 
> > Using other urlpaths:
> >
> > or split everypart into an own file:
> >
> >
> >
> > would be only a xmlfile that refers to the other parts.
> I think there's no need for separate files. These most likely would be
> handled on the server by the same service.
> Because to provide extended config (e.g. identities) we need to
> authenticate user and because Mozilla actually does only configuration
> without authentication (and on http not https) I think we can use any
> (new) xml format in any URL we choose that starts with https:// and will
> require authentication.
> Thunderbird uses two locations:
> -
> .com -
> So, we could use also two, but I'd change http:// to https:// and
> config-v1.1.xml to kolab-v1.0.xml. That would be best from autoconfig
> service perspective.

I guess this depends on wether we break other clients with the new 
ldapProvider/freebusyProvider settings. If we don't I think we should stick to 
config-v1.1 (and remain within autoconfig), otherwise it probably makes sense to 
use kolab-v1.0.xml, but that would mean we're not autoconfig compatible.

So perhaps it does make sense to separate the config files and provide:

This is interoperability wise probably the best.


More information about the format mailing list