Full_Name: Michael Str�der Version: HEAD OS: URL: Submission from: (NULL) (79.227.170.198) Importing an LDIF file with slapadd which contains entries with an object class marked as OBSOLETE in the schema fails. Importing entries with OBSOLETE attribute types seems to work just fine. If object classes are marked as OBSOLETE it's clear that it should be impossible to add new entries via LDAP based on such an object class. But it should still be possible to restore old entries from backup.
> Full_Name: Michael Ströder > Version: HEAD > OS: > URL: > Submission from: (NULL) (79.227.170.198) > > > Importing an LDIF file with slapadd which contains entries with an object > class > marked as OBSOLETE in the schema fails. > > Importing entries with OBSOLETE attribute types seems to work just fine. > > If object classes are marked as OBSOLETE it's clear that it should be > impossible > to add new entries via LDAP based on such an object class. But it should > still > be possible to restore old entries from backup. Currently, slap_tool_entry_check() sets "manage" to 0 when calling entry_schema_check(); setting it to !0 would allow loading of OBSOLETE objectClasses. Maybe "manage" should be passed to slap_tool_entry_check(), and write tools (slapadd, slapmodify) could have an explicit '-o manage' option to enable handling of these cases. p. -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano
masarati@aero.polimi.it wrote: > Maybe "manage" should be passed to > slap_tool_entry_check(), and write tools (slapadd, slapmodify) could have > an explicit '-o manage' option to enable handling of these cases. I'd regard slapadd to be in kind of a manage mode by default. E.g. it does not check constraints. And as said OBSOLETE attribute types are already accepted. Ciao, Michael.
Need to review slapadd behavior in this case. Possibly add -o manage option to flip the manage bit to true
changed notes moved from Incoming to Software Bugs