To demo the new feature run

sudo DEBUGGING=True py.test-3 dirsrvtests/tests/suites/ds_tools/replcheck_test.py

Edit dse.ldif for "slapd-master2" to allow LDAPI autobinds, then start "slapd-master2"

Then goto the UI and you will see some conflict and glue entries to play around with under the monitor tab --> replication.

To demo the new feature run
sudo DEBUGGING=True py.test-3 dirsrvtests/tests/suites/ds_tools/replcheck_test.py
Edit dse.ldif for "slapd-master2" to allow LDAPI autobinds, then start "slapd-master2"

When I do this, it shows me the next error while loading...

{"desc": "Inappropriate authentication", "info": "SASL EXTERNAL bind requires an SSL connection"}

I have F29 with the 389-ds-base built from this branch.

Then goto the UI and you will see some conflict and glue entries to play around with under the monitor tab --> replication.

@spichugi, Weird, does the test it self run, then it fails in the UI after making the dse.ldif change?

I just make sure these attributes are set (while the server is shutdown):

nsslapd-ldapilisten: on
nsslapd-ldapiautobind: on

Then I can load "master2" in the UI

Yeah, I missed the LDAPI change before. So maybe it was the cause.

LGTM! Ack

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3397

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.