[Kolab-devel] Kolab user management

[Cajus Pollmeier]

Am Mittwoch, 23. März 2005 14:33 schrieb Martin Konold:
> Am Mittwoch, 23. März 2005 11:47 schrieb Cajus Pollmeier:
>
> Hi Cajus,
>
> > looking at the kolabDeleteflag, it seems to request a complete delete of
> > the DN which contains it - if I'm interpreting the perl code correctly.
> > Technically this is a problem for tools like LAM or GOsa, because they
> > might want to remove the Kolab aspects of an account, only.
>
> Yes, this is indeed an issue. But how often is the plain removal of the
> Kolab aspect only a requirement?

Hi Martin,

this is more a functional issue. In this case I can only speak for GOsa 
functionality, where several parts like i.e. Proxy, Posix, Samba, Mail, etc. 
are handled as such an account aspect. They can be added and removed without 
the need of removing the complete entry.

> > Besides the handling of mailboxes and alias cleanups, are there
> > additional things you take care of when the delete flag is set?
>
> The LDAP admin tool has not to take care of anything like these. This is
> the job of the kolabd which does not care you made the appropriate settings
> in the LDAP repository.

That was not the question. Lets say it this way: I'm not going to use kolabd 
for account removal, as long as the point from above is not working as 
expected. Ergo I've to care about these things myself:

What would kolabd do besides removing of mailboxes, alias cleanups and the 
removal of the specified DN from LDAP?

> > Are kolabOrganizationalUnit
>
> basically it is a normal OrganizationalUnit plus deleteflag. Please check
> with kolab2.schema for further details.
>
> > interpretation somewhere? Or what do you mean by "We use kolabNamedObject
> > in order to put more structure in the directory tree"?
>
> We want to easily find the base dn for kolab in a potentially big LDAP
> tree.

The question was if "kolabOrganizationalUnit" and "kolabNamedObject" are used 
somewhere in the code. I've read your schema definitions carefully, but I'd 
like to avoid reading the complete sourcecode.

Cheers,
Cajus