[Kolab-devel] [PATCH] Fix for kolab webclient metoo function on forwarding

[Jan Schneider]

Zitat von Dan Ohnesorg <Dan at ohnesorg.cz>:

> Dne Mon, Dec 01, 2003 at 12:36:30PM +0100, Jan Schneider napsal:
>
> > > I have just found, that I am not able to send meeting request - there
> is
> > > not
> > > default account set and moment needs them.
> >
> > That's right, you need to create an identity first. If user information
> is
> > stored on the Kolab server, this could be done automagically by a hook
> on
> > first time login.
>
> I dont like this idea too match. If You will copy the setting, any change
> made over kolab admin interface won't be reflected in the user identity.

It will, if you lock the prefs. But then the users won't be able to change
these settings.

> I have seen, that someone had alerady solved a part of the prefs storage.
> I
> have made the same, just enabling LDAP works and stores the preferencies.
> Yes you need extend LDAP, but its the LDAP nature, be so extended to hold
> any info about user on one place for all the systems (and make replicas
> to
> prevent data loss and better performance).
>
> You will only go into problem by users, which don't have needed
> objectClass,
> so I have patched ldap.php to check it and if needed extend the user to
> hordePerson, so the saving sucess. This should be probably part od horde,
> not part of kolab, because any ldap backend will have problem with user,
> which don't have proper object class.

Not sure if I follow you here, but I'm no ldap expert at all. I'll forward
your mail the horde mailing list, you should subscribe there for
in-depth-dicussions.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft