Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates


Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
Prev	Performing a VCS upgrade using the installer	Next

Note that you must perform the following tasks after upgrading to 2048 bit key and SHA256 signature certificates:

Delete certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates.

See Deleting certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates.
Re-establish WAC communication in global clusters after upgrading to 2048 bit key and SHA256 signature certificates.

See Re-establishing WAC communication in global clusters after upgrading to 2048 bit key and SHA256 signature certificates.
Re-establish communication between Steward and upgraded clusters.

See Re-establishing trust with Steward after upgrading to 2048 bit key and SHA256 signature certificates.

Note:

The cluster communication between global clusters breaks if the cluster on one site is running VCS 7.2 and the other is on VCS version lower than 6.0.5. If you upgrade to 2048 bit key and SHA256 signature certificates in such a configuration, the communication will not be restored even after performing the essential tasks after the upgrade. The only workaround for this is to upgrade VCS to version 6.0.5 or above on clusters which are running on VCS versions lower than 6.0.5.

Prev	Up	Next
Upgrading to 2048 bit key and SHA256 signature certificates	Home	Deleting certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates