How to replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Active Directory Certificate Authority
7 hours ago
Originally Published: 2017-03-15
Article Number
000042325
Applies To
Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
This article explains how an RSA administrator would replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Active Directory Certificate Authority.
Resolution
  1. From the Operations Console select Deployment Configuration > Console Certificate Management.
  2. Click Generate CSR.
User-added image
  1. Under Certificate Basics, fill in the certificate information.
  2. Click Generate File.
User-added image
  1. Download the CSR then open it with a text editor and copy the file content.
User-added image
  1. On the Active Directory CA server, go to https://localhost/certsrv or https://<Active Directory_CA_FQDN>/certsrv:
User-added image
  1. Click the link to submit an advanced certificate request.
User-added image
  1. Click the option to submit a certificate request using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.
User-added image
  1. Under Saved Request paste the CSR file content into the box labeled Base-64-encoded certificate request (CMC or PKCS #10 or PKCS #7).
  2. For Certificate Template make sure to select Web Server.
  3. Click Submit.
User-added image
  1. Click Download Certificate Chain.
User-added image
  1. From the Operations Console select Deployment Configuration > Console Certificate Management.
  2. Select PKCS#7 (.cer or .p7b) for the Type of Certificate to import. 
  3. Choose Import Certificate.
  4. Click Activate.
User-added image
  1. Review the certificate details to ensure this is the certificate you wish to activate.
  2. Place a check in the Activate Certificate Confirmation box.
  3. Click Activate Certificate.
User-added image
  1. After selecting Activate Certificate, the Authentication Manager services will be restarted automatically.

Verify: Once services have restarted, open a web browser and navigate to the Operations Console URL. Confirm that:

  • The browser displays no certificate warnings
  • The certificate issuer matches your Microsoft AD CA
  • The certificate expiry date is correct
Notes
  • Certificate Expiry — Plan for Renewal: Certificates issued by Microsoft AD CA are typically valid for 1–2 years. If the console certificate expires and Authentication Manager services are stopped, the services cannot restart until the expired certificate is replaced with a valid one. Monitor the expiry date noted in Step 21 and plan renewal ahead of time.

  • Replica Instances: This procedure replaces the console certificate on the primary Authentication Manager instance only. If your deployment includes replica instances, verify whether the certificate change propagates automatically or requires a separate procedure on each replica.

  • Certificate Format — PKCS#7 Required: Authentication Manager requires the certificate to be imported in PKCS#7 (.cer or .p7b) format. If your AD CA offers a DER or PEM format instead of a certificate chain, contact your CA administrator to request the full certificate chain in PKCS#7 format.

  • Third-Party CAs: The CSR generation and certificate import steps in this article are the same for any CA. Only the submission process (Part 2) differs. For third-party CA instructions, refer to your CA vendor's documentation.

  • Related Article: For background on how RSA Authentication Manager uses self-signed certificates for internal component communication (and why those should not be replaced), see RSA Authentication Manager and Self-Signed Certificates — KB 000068458.