此内容没有您所选择的语言版本。
10.3. Updating CA-KRA Connector Information After Cloning
As covered in Section 2.7.9, “Custom Configuration and Clones”, configuration information is not updated in clone instances if it is made after the clone is created. Likewise, changes made to a clone are not copied back to the master instance.
If a new KRA is installed or cloned after a clone CA is created, then the clone CA does not have the new KRA connector information in its configuration. This means that the clone CA is not able to send any archival requests to the KRA.
Whenever a new KRA is created or cloned, copy its connector information into all of the cloned CAs in the deployment. To do this, use the
pki ca-kraconnector-add
command.
If it is required to do this manually, follow these steps:
- On the master clone machine, open the master CA's
CS.cfg
file, and copy all of theca.connector.KRA.*
lines for the new KRA connector.vim /var/lib/pki/instance_name/ca/conf/CS.cfg
[root@master ~]# vim /var/lib/pki/instance_name/ca/conf/CS.cfg
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Stop the clone CA instance. For example:
systemctl stop pki-tomcatd@instance_name.service
[root@clone-ca ~]# systemctl stop pki-tomcatd@instance_name.service
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Open the clone CA's
CS.cfg
file.vim /var/lib/pki/instance_name/ca/conf/CS.cfg
[root@clone-ca ~]# vim /var/lib/pki/instance_name/ca/conf/CS.cfg
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Copy in the connector information for the new KRA instance or clone.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Start the clone CA.
systemctl start pki-tomcatd@instance_name.service
[root@clone-ca ~]# systemctl start pki-tomcatd@instance_name.service
Copy to Clipboard Copied! Toggle word wrap Toggle overflow