Kolab / Horde LDAP missmatch?

[Aaron J. Seigo]

On Tuesday 02 August 2005 01:42, you wrote:
> On Monday 01 August 2005 19.08, Aaron J. Seigo wrote:
> > yes, i have a local fix for this...
> > in /kolab/var/kolab/www/admin/user/user.php on or around line 453 you'll
> > see this:
> >
> >        $ldap_object['objectClass'] = array('top',
> > 'inetOrgPerson','kolabInetOrgPerson');
> >
> > change it to:
> >
> >        $ldap_object['objectClass'] = array('top', 'inetOrgPerson',
> > 'kolabInetOrgPerson', 'hordePerson');
> >
> > and voila, things are good, even for accounts that have never been used
> > with horde. AFAIK this is not currently a generic fix since kolab doesn't
> > ship with the horde LDAP schema (which contains hordePerson) so would
> > likely create errors for those w/out horde.
>
> It should not be to hard to check if horde.schema is included in the ldap
> config files and based on that conditionally use the correct one.

might that not be a bit slow?

would it make more sense to have another checkbox on the services page that 
says "Enabled Horde webmail integration" and have the admin turn that on?

either way, i don't particularly care. i'll leave it up to the kolab web admin 
maintainer. choose a way and i'll implement it immediately and present the  
patch on the list here.

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20050802/17b90ff9/attachment.sig>