Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
There might not be any way to handle this specific issue. Might be an oversight in the design. However a solution is simple I think. We just need to really delete the entry marked for deletion and add the new entry with the same dn in it's place.
Here's the error I get from the server when trying to add the entry after having deleted it:
Root error: [LDAP: error code 68 - failed to add entry ou=neworganizationalUnit,dc=example,dc=com: 2.5.4.11=neworganizationalunit,0.9.2342.19200300.100.1.25=example,0.9.2342.19200300.100.1.25=com already exists.]
which means ...
LDAP_ALREADY_EXISTS: Indicates that the add operation attempted to add an entry that already exists, or that the modify operation attempted to rename an entry to the name of an entry that already exists.