Andreas 'ads' Scherbaum wrote:
Hello all,
i tried to update an openldap server from 2.2.13 to 2.3.27 but ran into problems. The slapd is using back-sql to get data from an existing PostgreSQL groupware database. This worked fine with the 2.2 version, but after the update the client (Thunderbird in my case) no longer gets data. According to wireshark, no data is sent back to the client.
Testing with a local ldapsearch brings results, but with the following differences:
----- 2.2.13 ----- objectClass: orgPerson objectClass: inetOrgPerson objectClass: officePerson objectClass: evolutionPerson objectClass: top objectClass: opengroupwareentity objectClass: person ----- 2.2.13 -----
----- 2.3.27 ----- objectClass: person objectClass: evolutionPerson objectClass: inetOrgPerson objectClass: opengroupwareentity objectClass: top ----- 2.3.27 -----
The 'ldap_objectclass_list' table contains the following entries:
----- cut ----- OGo=# select * from ldap_objectclass_list; oc_map_id | objectclass -----------+--------------------- 1 | orgPerson 1 | inetOrgPerson 1 | officePerson 1 | evolutionPerson 1 | top 1 | opengroupwareentity 3 | top 3 | opengroupwareentity 4 | top 4 | domainRelatedObject (10 rows) ----- cut -----
Has anybody an idea why the ldapsearch returns fewer entries for the objectClass? That should be the reason, why no data is sent back to the client.
ldap_objectclass_list is not used by back-sql; I guess you mean ldap_entry_objclasses (unless you modified the source yourself).
In any case, I note that the missing objectclasses, namely orgPerson and officePerson, are not standard track types. Are they defined anywhere in the schema? One of the differences between 2.2 and 2.3 is a stricter checking of the schema.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------