Implementing private certificates in the TrueSight Infrastructure Management
The following section guides you to create a signed certificate for the Infrastructure Management server and the cell component.
Before you begin
Before creating a private certificate for the Infrastructure Management server and securing the communication, ensure the following:
- Create a private certificate for the Remedy Single Sign-On Server and secure it.
- Create a private certificate for the TrueSight Presentation Server and secure it.
BMC Confidential. The following information is intended only for registered users of docs.bmc.com.
Where to go from here
Once you secure the TrueSight Infrastructure Mnagement, you can apply this certificate to other TrueSight Operations Management components such as:
- Applying Infrastructure Management server and the cell certificate to the TrueSight Presentation Server.
- Applying Infrastructure Management server and the cell certificate to the TrueSight Integration Service.
- Applying Infrastructure Management server and the cell certificate to the Impact Integration Web Services.
- Applying Infrastructure Management server cell certificate to IT Data Analytics.
- Applying Infrastructure Management server cell certificate to the Publishing Server.
You can also explore how to implement private certificates in other TrueSight Operations Management components.
Was this page helpful? Yes No
Submitting...
Thank you
Comments
keytool -importkeystore -deststorepass get2net -destkeypass get2net -destkeystore pnserver.ks -srckeystore tsimserver.p12 -srcstoretype PKCS12 -srcstorepass bmcAdm1n returns an error 'keytool error: java.io.IOException: keystore password was incorrect'. tsimserver.p12 keystore's password does not seem to be bmcAdm1n as mentioned.
Solved it adding the password when executing 20) openssl pkcs12 -export -out tsimserver.p12 -inkey tsimSrv.key -in tsim.cer -certfile ca.cer (export password). Could you please clarify ?
Thanks for the feedback.
I will discuss with the team and update the documentation.
Hi,
Thankyou for the inputs.
I have updated the Note in step # 20 that informs the user to note the .p12 file password for later references.
I can't get #19 to work. It just dumps the Usage for pkcs12
openssl pkcs12 -export -out tsimserver.p12 -inkey tsimSrv.key -in tsim.cer -certfile ca.cer -certfile Usage: pkcs12 {options} where options are
got it figured out. Had a coworker help me...
openssl pkcs12 -inkey tsimSrv.key -in server.cer -certfile rootca.cer -export -out tsimserver.p12
Thankyou for this update.
Log in or register to comment.