How can you update the Portal keystore with a new keypair, without reverting the configuration?
book
Article ID: 281370
calendar_today
Updated On:
Feedback
Subscribe
Products
Network Observability
CA Performance Management
Show More
Show Less
Issue/Introduction
We need to update the NetOps Portal with a new keypair, but would like to avoid reverting to http due to security restrictions
Environment
All DX NetOps Performance Management releases
Resolution
Find the keystore name, keystore password, and alias of the existing keystore
This can be done with a keytool -list command, for example:
keytool -list -keystore keystore
Backup the existing truststore and keystore
By default, these two files need to be backed up
/opt/CA/PerformanceCenter/jetty/etc/keystore
/opt/CA/jre/lib/security/cacerts
Generate or obtain a new keystore
This can be done either through an existing keystore, or following the below kb article if given a private key and public certificate
Alter the new keystore to mirror the existing keystore
This is ideally done when generating the keystore, but if not, you can alter things like the alias through commands as illustrated within this kb article:
Import the root & intermediate certs into the truststore
The root certificate will need to be trusted. If the certificate chain is proper, the intermediate should not require explicit trusting
/opt/CA/jre/bin/keytool -importcert -keystore cacerts -alias root_cert -file root.pem
stop all 4 caperfcenter services
move the new keystore into the old keystore's location
start all 4 caperfcenter services
systemctl start caperfcenter_sso caperfcenter_eventmanager caperfcenter_devicemanager caperfcenter_console
Feedback
thumb_up
Yes
thumb_down
No