How to create an Extended Validation (EV) compatible Root CA?
Originally Published: 2008-06-09
Last Modified: 2023-11-30
Article Number
Applies To
Issue
The profiles "EV SSL Root CA" and "EV SSL Subordinate CA" are not in the list of extension profiles to choose from when creating a CA
Resolution
To correct this, you must edit the Extension Profiles for those selections.
1. Access the RCM Administrative UI.
2. Go to the "System Configuration" workbench -> Extension Profiles
3. Select the profile named "EV SSL Root CA", click on Edit.
4. Change the Profile Type from "End entity" to "CA", then click Save.
Do the same thing with the profile "EV SSL Sub-ordinate CA".
Now when you go to create a new CA, at the jurisdiction configuration page during it's creation, in the Sections drop down, select Extension Profiles.
Select all profiles in the list (or only those you will need), click on Save and continue.
Select the extensions profile "EV SSL Root CA" or "EV SSL Subordinate CA" when creating your CA.
Related Articles
Cherry Smart Card-Reader stops working after the RSA Authentication Agent for Windows is installed Number of Views How to create a CA hierarchy where one subordinate CA uses SHA1 and another subordinate CA uses SHA2 while both sub CA's … Number of Views Want to pass a configuration file to the FIM 3.0 / 3.1 Bulk Federation Utility Number of Views Capture the reserve password from the current RSA ACE/Agent 5.6 for Windows installation is grayed out Number of Views Import a Signed Virtual Host Certificate Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?
