389-ds-base

#50609 monitoring replication via anonymous srch on cn=monitor
Closed: wontfix by spichugi. Opened by tbordaz.

Closed: wontfix
Reopen Issue

Issue Description

Currently monitoring replication is done via a search of nsds50ruv on "cn=replica,cn=,cn=mapping tree,cn=config" that requires privilege.

So to monitor a full topology, it requires to store the DM password of each server that is complex/sensitive.

Would it be possible, for example during RUV write back thread, to update a monitor entry.
I order to hide the server url, only replicaID would be stored in addition to csn.
For not replicated backend, no 'replicaID' attributes are stored.

dn: cn=monitor
...
nbackends: 3
backendmonitordn: cn=monitor,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
backendmonitordn: cn=monitor,cn=ipaca,cn=ldbm database,cn=plugins,cn=config
backendmonitordn: cn=monitor,cn=changelog,cn=ldbm database,cn=plugins,cn=config
dn: cn=replication,cn=monitor
dn: cn=userRoot,cn=replication,cn=monitor
..
replicaId: 1 57fe0206000700010000
replicaId: 2 57fe020a000000020000
replicaId: 6 57fe0b0a000000060000
dn: cn=ipaca,cn=replication,cn=monitor
..
replicaId: 11 57fe53060007000b0000
replicaId: 12 57fe530a0000000c0000
replicaId: 16 57fe4b0a000000100000
dn: cn=changelog,cn=replication,cn=monitor

Package Version and Platform

N/A

Steps to reproduce

NA

Actual results

monitoring of replication requires credential

Expected results

monitoring of replication can be done anonymously

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

Include nsState?

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4 backlog (was: 1.4.2)
- Issue tagged with: RFE

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

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
- Issue status updated to: Closed (was: Open)
Metadata
None

RFE

None
None
High
None
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.