Red Hat CERTIFICATE SYSTEM 7.2 - MIGRATION GUIDE Manual page 106

Enter password for PKCS12 file: ********
pk12util: PKCS12 IMPORT SUCCESSFUL
pk12util -i kraTransportCert.p12 -d .
Enter Password or Pin for "NSS Certificate DB":********
Enter password for PKCS12 file: ********
pk12util: PKCS12 IMPORT SUCCESSFUL
8. Optionally, delete the PKCS #12 files.
rm ServerCert.p12
rm kraStorageCert.p12
rm kraTransportCert.p12
9. Set the trust bits on the public/private key pairs that were imported into the new security databases.
certutil -M -n "Server-Cert cert-old_DRM_instance"
-t "cu,cu,cu" -d .
certutil -M -n "kraStorageCert cert-old_DRM_instance"
-t "u,u,u" -d .
certutil -M -n "kraTransportCert cert-old_DRM_instance"
-t "u,u,u" -d .
10. Import the public key from the base-64 file, and set the trust bits.
certutil -A -n "caSigningCert cert-old_DRM_instance"
-t "CT,c," -d . -i caSigningCert.b64
11. Optionally, delete the base-64 file.
rm caSigningCert.b64
12. Open the CS.cfg configuration file.
cd /var/lib/instance_ID/conf/
vi CS.cfg
13. Edit the kra.storageUnit.nickname and kra.transportUnit.nickname attributes to reflect the new
DRM instance.
kra.storageUnit.nickname=
kraStorageCert cert-old_DRM_instance
kra.transportUnit.nickname=
kraTransportCert cert-old_DRM_instance
NOTE
The caSigningCert is not referenced in the CS.cfg file.
14. In the same directory, edit the serverCertNick.conf file to contain the old certificate nickname. For example:
vi serverCertNick.conf
Server-Cert cert-old_DRM_instance
5.2. 6.1 and 6.2 Data Recovery
Manager (DRM) Migration
Databases