[Kolab-devel] Kolab user management
Stephan Buys
list at codefusion.co.za
Wed Mar 23 07:13:12 CET 2005
Hi,
On Tuesday 22 March 2005 18:35, Roland Gruber wrote:
> ok, this looks like I only have to create LDAP accounts and the kolabd
> will do the rest automagically. No need to call any scripts from my side.
>
Correct, just populate the correct attributes in LDAP.
> > Best for you would be to have a running Kolab2 Server as example.
> > What happens it that we have regular users and one kolab server object
> > and each ldap change gets distributes towards the kolabd component.
> > This is a daemon that will take action when ldap changes,
> > it creates mailbox accounts in cyrus, sets permissions there
> > and on seeing the kolabldeleteflag, it will clean up and then delete the objects
> > from the ldap.
>
> What do you mean with it deletes objects from LDAP? Are there different
> accounts for completed users and those who need to go through the kolabd
> process?
All accounts look the same. We just add the kolabDeleteFlag attribute to the
object when it comes time to delete the account. The Kolab Daemon then
goes around, clears the Cyrus mailboxes and deletes the object out of LDAP.
> What about modifying accounts, will kolabd also update the existing
> accounts?
One of the only items that will affect the Kolab account is the Quota of
the user mailbox. This again is handled by the daemon and all you have to do
is set the right values in LDAP.
> At the moment it looks like being not very hard to implement, just a
> question of time. ;-)
The really great thing about Kolab is that it is LDAP-centric. You make your
changes in LDAP and it then trickles down to the various daemons.
Regards,
--
Stephan Buys
Code Fusion cc.
Tel: +27 11 673 0411
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za
E-mail Solutions, Kolab Specialists.
http://www.codefusion.co.za
More information about the devel
mailing list