Add pki-server <subsystem>-db-repl-agmt-init #4636
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
pki-server <subsystem>-db-repl-agmt-init
has been added to start initializing the replication agreement and wait until it's complete.The
SubsystemDBReplicationSetupCLI
has been modified to no longer include initializing the replication agreement.The test for CA cloning with replicated DS has been updated to use the new command. The test has also been updated to
import the primary CA's system certs and keys into the secondary CA's NSS database prior to running
pkispawn
so it's no longer necessary to specify the PKCS #12 path and password forpkispawn
.The
ConfigurationFile.verify_predefined_configuration_file_data()
andinitialization.py
have been modified such that the PKCS #12 path and password are no longer mandatory for cloning.https://github.com/dogtagpki/389-ds-base/wiki/Configuring-DS-Replication-with-DS-Tools
https://github.com/dogtagpki/389-ds-base/wiki/Configuring-DS-Replication-with-LDAP-Tools
https://github.com/dogtagpki/389-ds-base/wiki/Configuring-DS-Replication-with-PKI-Tools