If you recreate the Root CA on a BoKS Master the BoKS Control Center (BCC) Presentation Server will no longer be able to communicate with the Admin Server (bccasd) on the BoKS Master.
In order to resolve this you will need to recreate the Java Keystore file (trustfile.jks) on the BoKS Control Center Presentation Server (which may or may not be running on the Master) with the correct Host Certificate, Private Key and CA Chain.
You will need to use two different utilities to achieve this: bccgethostcert(on the Master) and createtrust.sh (on the BCC Presentation Server).
Note: When running the bccgethostcert command you will be prompted to enter a password for the PKCS#12 file. It is important to enter the same password as used for the Java Keystore file. The keystore password is available in $BCCPS_etc/bcc.properties.
Replace "bcc_hostname" with the actual hostname of the BCC server in the example above.
Note: You should rename the current keystore file before running this command. The trustfile is located in /etc/opt/bccps/ by default.
The communication from the BCC Presentation Server to the bccasd server in BoKS can be verified by running $BCCPS/sbin/pingbccas.sh.
Run pingbccasd.sh to verify that the communication is now functioning correctly with the certificates from the new keystore.
If all is functioning correctly, BCC can be restarted to pick up the new Java Keystore.