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
Maintain Authentication Agent Associations in a Duplicated User Group Number of Views Delete a Replica Instance Number of Views Cloud Administration System Event Log API Number of Views Import a Signed Virtual Host Certificate Number of Views Log Rotation Policy for the Appliance Logs Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA-2026-07: RSA Identity Router Security Update for Third-Party Component Vulnerabilities
