Kolab / Horde LDAP missmatch?

[Aaron J. Seigo]

On Monday 01 August 2005 10:05, Uwe Weiss wrote:
> But after my first login to horde, it's not possible to change account data
> within the Kolab manger Website anymore. I always receive the Error 'LDAP
> Error: Could not modify object cn=test tester,dc=valeosurf,dc=com: Object
> class violation'

> Has anyone any ideas?

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.

-- 
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/20050801/168eb61b/attachment.sig>