BMC Confidential. The following information is intended only for registered users of docs.bmc.com.
Where to go from here
When you finish securing the Atrium Single Sign-On server, you can apply this Atrium Single Sign-On server certificate to other TrueSight Operations Management components, as described in the following procedures:
- Applying Atrium Single Sign-On Server private certificate to the TrueSight Presentation Server.
- Applying Atrium Single Sign-On Server private certificate to the TrueSight IT Data Analytics.
You can also explore how to implement private certificates in other TrueSight Operations Management components.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
8 Comments
Charles Kelley
Rashmi Gokhale
Hi Charles,
Have modified the statement that conveys that if there are any existing ASSO certificate aliases delete them.
Thanks,
Rashmi
Charles Kelley
Rashmi Gokhale
Mahesh Darekar
In Steps 7 and 8
Do you know why do we need to change filename from keystore-update.p12 to keystore-update.ks without any reason? Is this typo?
To verify that tomcat alias is created, list the keystore file by running the following command:
Verify the alias entry by listing the keystore file
keytool -list -keystore keystore-update.ks -storepass changeit -storetype JKSRashmi Gokhale
Hi Mahesh,
Thanks for the observation. I have fixed the typo.
Thanks,
Rashmi
Benarjee Tumati
There are some errors in the document, I have followed the below link where
Johann Groenewald has clear instructions in the comments on how to do that.
https://docs.bmc.com/docs/display/public/sso90/Creating+a+new+key+pair
Rashmi Gokhale
Hi Tumati,
Thank you for the feedback.
I checked the instructions provided by Johann on the SSO page. Have corrected the store type as PKCS12.
Regarding the key pair generation instruction when SSO is in high availability mode, I will check with an SME and update the instruction.
Thanks,
Rashmi