389-ds-base

#375 replication should send raw, unnormalized DNs to consumer
Closed: wontfix Opened by rmeggins.

Closed: wontfix
Reopen Issue

1.2.11 currently sends normalized DNs/RDNs to consumers. Consumers must have access to the raw data so that things like modrdn rename (i.e. just changing the case of the DN without changing the actual DN) can be replicated.

Added initial screened field value.

Metadata Update from @nkinder:
- Issue assigned to rmeggins
- Issue set to the milestone: N/A

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/375

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 Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)
Metadata
None
None
None
Low
no review needed
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.