Bugzilla – Bug 563796
client's ldap_schema_save call causes error 0x50 to be returned from server
Last modified: 2012-02-17 09:09:12 UTC
When trying to add an optional attribute to the "inetOrgPerson" class using the 10-29-09 cldapsdk, calling ldap_schema_save returns an error of 0x50. Running ndstrace on the SLES10SP3 server with eDirectory 8.8.5 installed shows the following with tag LDAP enabled: Illegal ndsname "[Self]" in ldap2uNDSDN, err = 34 (0x22) ldapuNDSDN ldapDN = "[Self]" - error 34 (0x22) Illegal ndsname "[Self]" in ldap2uNDSDN, err = 34 (0x22) ldapuNDSDN ldapDN = "[Self]" - error 34 (0x22) Illegal ndsname "[Public]" in ldap2uNDSDN, err = 34 (0x22) ldapuNDSDN ldapDN = "[Public]" - error 34 (0x22) Illegal ndsname "[Self]" in ldap2uNDSDN, err = 34 (0x22) ldapuNDSDN ldapDN = "[Self]" - error 34 (0x22) Duplicate LDAP class name: "inetOrgPerson" (ignored) The same code is used to add other optional attributes to newly defined classes with no problem; it is only when adding optional attributes to the "inetOrgPerson" class (should map to "User") that this occurs. This code is used by Novell Messenger Linux installs to extend the schema. The install is failing against 8.8.5 eDirectory. Note 1: This same error was returned with a much older version of the cldapsdk (October 2004). Note 2: This code has worked fine until just recently reported against 8.8.5 and possibly 8.8.4 Blocks #525637