How to upgrade to Sentry CA 3.6 from a previous version of Sentry CA.
Originally Published: 2001-07-09
Last Modified: 2023-10-06
Article Number
Applies To
TechNote 0170
Issue
The instructions for upgrading from a previous version of Sentry CA to Sentry CA 3.6 are not included on the product cdroms. There are also steps that need to be done before and after to leave the gid at the correct value.
Resolution
As well as following the instructions in this document, you must also do the following:
1. Before upgrading your existing Sentry CA database, through the Administration web server, go to
https://<ca_hostname>:<admin_port>/ca/admin/listuobjects.xuda?objectclass=gid
and click edit.
2. Record the value under Current Attribute for GID.
3. Complete your upgrade as documented in the Sentry Upgrade Tool.
4. Once you have restarted your services, again go to
https://<ca_hostname>:<admin_port>/ca/admin/listuobjects.xuda?objectclass=gid
and click edit.
5. Change the Current Attribute for GID to match what you recorded in step 2.
Related Articles
Important information on upgrading to Sentry CA 3.7 from a previous version. 3Number of Views Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle 6Number of Views Attribute Change Rule reverts to a previous version after making changes in RSA Identity Governance & Lifecycle 27Number of Views Installation of 7.1.1 on SLES 12 SP4 fails with 'Pre-Requisites Test(s) failed' message on xorg-x11-server* files in RSA I… 46Number of Views Create Account fails if previous Create Account is pending in RSA Identity Governance & Lifecycle 115Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…
Don't see what you're looking for?