389-ds-base

#49077 [1.2.11 only] DN normalization should be the same than in 389-ds-base-1.3.X
Closed: wontfix Opened by nhosoi.

Closed: wontfix
Reopen Issue 
Description of problem:
This issue is similar to this bug fixed some time ago:
https://fedorahosted.org/389/ticket/48223
for winsync.
In this case DN normalization at import time is considering that, for instance,
these two dn's are duplicated:
================================
dn: cn=user nuevo,ou=people,o=redhat
objectclass: inetorgperson
cn: user nuevo
sn: usernuevo
userpassword: user49
dn: cn=user  nuevo,ou=people,o=redhat
objectclass: inetorgperson
cn: user  nuevo
sn: us
userpassword: user49
================================
errors:
[04/Jan/2017:15:02:50.356169698 +0100] entryrdn-index - _entryrdn_insert_key:
Same DN (dn: cn=user nuevo,ou=people,o=redhat) is already in the entryrdn file
with different ID 53.  Expected ID is 54.
[04/Jan/2017:15:02:50.399342349 +0100] import userRoot: Duplicated DN detected:
"cn=user nuevo,ou=people,o=redhat": Entry ID: (54)
To reproduce, just import both entries in the same ldif file.
not sure if this is, in fact a feature (it does not seem to me from rfc4514) or
if fixing this could break something else.
If this is not corresponding or too risky, let's close this.
Thanks.
German.

Thanks to German for figuring out the cause. It's likely this bug was introduced by the ticket 47720.
{{{
(In reply to German Parente from comment #2)

probably related to this ?

https://fedorahosted.org/389/ticket/47720

==========
else if (ISSPACE(s)) {
while (ISSPACE(s)) {
s++;
===========

that seems to be the difference in DN norm. from rhds9 code.
}}}

See also the closed bug: https://bugzilla.redhat.com/show_bug.cgi?id=1410131.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.2.11.33

This is a backport request to 1.2.11

Metadata Update from @mreynolds:
- Issue close_status updated to: None

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.2.11 (was: 1.2.11.33)

Closing too risky for 1.2.11

Metadata Update from @mreynolds:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2136

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
None
Normal
RHCust
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.