Replacing the Default Virtual Host Certificate
The following is the procedure for replacing the default virtual host certificate.
Procedure
Generate a certificate signing request using one of the following methods.
RSA Security Console. For instructions, see Generate a Certificate Signing Request (CSR) for the Web Tier.
Third-party tool. Ensure that the third-party tool generates a private key and a signing request. Ensure that you enter a common name (CN) where the value is the fully qualified hostname (FQHN) of the virtual host or you will not be able to activate the virtual host certificate. For instructions, see the third-party tool documentation.
Send the certificate signing request to the certificate authority (CA).
Import the trusted root and signed virtual host certificates and make it the active certificate. For instructions, see Import a Signed Virtual Host Certificate.
Update each web tier after importing the new certificate. For instructions, see RSA Authentication Manager Updates.
Related Concepts
Related Articles
Delete a Replica Instance Number of Views Hardware Appliance System Image Installation Number of Views Promote a Replica Instance for Disaster Recovery Number of Views Maintain Authentication Agent Associations in a Duplicated User Group Number of Views Assign Tokens to Users Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Identity Governance & Lifecycle Attribute Synchronization fails with Access Fulfillment Express (AFX) error
