Important information on upgrading to Sentry CA 3.7 from a previous version.
Originally Published: 2001-07-09
Article Number
Applies To
Keon Certificate Authority
TechNote 0206
Issue
This applies to existing Sentry CA 3.5 and 3.6 installations.
Resolution
1) When installing Sentry CA 3.7, the Common Name for the Root CA and the
Administrative CA must be different from the existing installation. This is
because the databases will be merged and two CAs within one installation
of Sentry CA may not have the same Common Name.
2) The database merge will combine the original ACL rules with the new ACL
rules. This generally means access to /ca/ will be open to certificates issued
by the original Administrative CA and the 3.7 Administrative CA. If desired, the
ACL rule can be changed to allow access only to the certificates issued by the
original Administrative CA. At this point, the 3.7 Administrative CA is no longer
used and can be suspended.
It is recommended to contact RSA Support for assistance in planning/deploying an upgraded CA installation.
Related Articles
How to upgrade to Sentry CA 3.6 from a previous version of Sentry CA. Number of Views Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle Number of Views Attribute Change Rule reverts to a previous version after making changes in RSA Identity Governance & Lifecycle Number of Views Create Account fails if previous Create Account is pending in RSA Identity Governance & Lifecycle Number of Views On systems where the BINDING_ATTR value has been changed should the USERID_ATTR value also be changed? Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Event Monitor Messages for Cloud Access Service (1501 - 20406) How to test RSA Identity Router (IDR) Secure Connector connectivity to the RSA ID Plus Cloud Access Service RSA Release Notes for RSA Authentication Manager 8.8 Troubleshooting RSA MFA Agent for Microsoft Windows
Don't see what you're looking for?
