Cause: Using the Attribute Uniqueness plugin and performing an LDAP RENAME operation on an entry containing one of the attributes being tested for uniqueness by the plugin.
Consequence: LDAP RENAME operation fails with err 19 Constraint Violation - Another entry with the same attribute value already exists.
Fix: The Attribute Uniqueness code was doing comparisons of un-normalized values. The fix is to make sure comparisons are done between values normalized the same way.
Result: LDAP RENAME operations do not return err 19 when there is no conflict.