https://bugzilla.redhat.com/show_bug.cgi?id=474621 Resolves: bug 474621 Bug Description: If you add an entry using a create attribute in the RDN (such as nsuniqueid), the entry will be added, but the value used in the RDN will not exist in the entry. The same issue occurs with performing a MODRDN operation using a created attribute in the new RDN. Reviewed by: ??? Files: see diff Branch: HEAD Fix Description: The fix checks if the common created attributes are used as the RDN for both ADD and MODRDN operations. We disallow using nsuniqueid, creatorsName, modifiersName, modifiedTimestamp, and createTimestamp in the RDN for an external ADD operation. For a MODRDN, we disallow the same attributes in the new RDN with the exception of nsuniqueid. We want to allow nsuniqueid in the RDN from internal operations for replication conflict entries. The client will receive an LDAP_INVALID_DN_SYNTAX result if they violate the above rules. Platforms tested: F9 Flag Day: no Doc impact: no QA impact: should be covered by regular nightly and manual testing New Tests integrated into TET: none https://bugzilla.redhat.com/attachment.cgi?id=327773&action=diff