We should enforce that if an object is of type nsds5replica, it must be named cn=replica. This has caused some confusion where people have misconfigured their system by trying alternate names.
Valid: cn=replica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config
Invalid: cn=supplierreplica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config
I don't not remember if there are any other valid child objects of the suffix MT entry here, so I think this should be checked.
This is a common usability issue, and low resources to fix, so we should do it ASAP.
There is an assumption, we retrieving replica, that RDN is 'cn=replica'. I am not sure it worth the effort to support different RDN. But an option would be to update replica_config_add so that when a replica entry is added to check that its RDN is REPLICA_RDN. It looks a simple fix.
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
agreed, we should enforce cn=replica, if we would go the other way and make cn=somerplica work we would run into issues where several replica objects for a suffix would be added
Metadata Update from @gparente: - Issue assigned to gparente
https://pagure.io/389-ds-base/pull-request/50079
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.1
Metadata Update from @gparente: - Custom field reviewstatus adjusted to review (was: None) - Issue set to the milestone: None (was: 1.4.1)
Fixed in the former pull request.
Metadata Update from @gparente: - Issue close_status updated to: fixed - 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/3118
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)