[Kolab-devel] [issue965] always use calendar user instead of kolabEncryptedPassword

Bernhard Herzog kolab-issues at intevation.de
Thu Oct 27 19:14:41 CEST 2005

New submission from Bernhard Herzog <bh at intevation.de>:

With the current implementation of the automatic resource handling the
kolab server uses one of two ways to access the imap server with write
permissions into the default calendar folder of the recipient:

  1. a special user (calendar at ...) which has to be given write
     permissions on the default calendar folder.  This is the approach
     used for normal users.  The permissions have to be set manually.

  2. The kolabEncryptedPassword ldap attribute which contains an
     encrypted but decryptable form of the user's password.  This is
     only used for resource and group accounts.

Due to the way it's implemented, the calendar user also works for the
group/resource accounts, though, because it's used as a fallback when
the encrypted password doesn't exist.

Instead of these two approaches, the kolab server should only use the
calendar user.  For group and resource accounts this means that the
default calendar has to be created by the kolabd when the user is

assignedto: steffen
messages: 5751
nosy: bh, steffen
priority: bug
status: unread
title: always use calendar user instead of kolabEncryptedPassword
topic: kkc, server
Kolab issue tracker <kolab-issues at intevation.de>

More information about the devel mailing list