[Date Prev][Date Next]
Slappadd is tolerant with wrong ldif files (openldap 2.2.19). Is it possible to make it strict ?
I populate my openldap directory using slapadd with a ldif file released by someone else. It appears that, in that ldif file, the inetorgperson objects do not have the objectclasses organizationalPerson, person and top. There is no error during slapadd. Slapd works fine, but some programs that access to my directory are stricter thant slapadd and fail for the following reason: as there is no objectclass: top line in the object, the program does not allow the object to have objectclass attribute.
The RFC 2256 says that an object representing a user must have at least two objectclass attributes and one of them must be top or alias. I understand that slapadd imports objects that do not conform to RFC 2256.
I searched on openldap.org if it is possible to configure slapadd to be more strict with the ldif file but I did not find anything about that problem.
The version of OpenLDAP I use is 2.2.19, on Windows XP.
Is there an option to make slapadd really strict with the imported ldif file ?
MOIE SIC Terre
Tél : +33(0)1 41 30 29 65
Fax : + 33 (0)1 41 30 33 36
EADS Defence and Security Systems SA
Defence and Communications Systems
rue Jean-Pierre Timbaud
78063 SAINT QUENTIN YVELINES Cedex