[389-devel] Please review (take 2): [Bug 612771] RHDS 8.1/389 v1.2.5 accepts 2 identical entries with different DN formats

[Noriko Hosoi]

https://bugzilla.redhat.com/show_bug.cgi?id=612771

https://bugzilla.redhat.com/attachment.cgi?id=431976&action=diff

https://bugzilla.redhat.com/attachment.cgi?id=431976&action=edit

Thanks to Rich for the good idea  to enhance the procedure.
>  What if we do what replication conflicts do and rename the entry to
>  nsuniqueid=<uuid>+oldDN?  or use some other unique name?

Based upon the suggestion by Rich, in case duplicated DNs are found, the second
DN is renamed to nsuniqueid=<uuid>+oldDN (import_foreman in import-threads.c).

In addition, there was a bug to handle multi-valued RDNs in
slapi_dn_normalize_ext.  In case multi-valued RDN appears with DN value (e.g.,
nsuniqueid=<uuid>+cn=uid\=<uid>\,o\=<org>,dc=<dc>),
it was not normalized properly.  Introduced additional rdn_av_stack
(subinitial_rdn_av_stack) for the nested DN value.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/389-devel/attachments/20100714/2f1e0e3e/attachment.html