Guidelines and resources for upgrading to SecurID Governance & Lifecycle 7.5.2
3 years ago
Article Number
000067937
Applies To
RSA Identity Governance & Lifecycle 7.5.0 and older versions
SecurID Governance & Lifecycle 7.5.2
Issue
SecurID Governance & Lifecycle version 7.5.2 was released in November 2021.  Upgrading from earlier versions of SecurID Governance & Lifecycle (or RSA Identity Governance & Lifecycle), such as 7.5.0, 7.2.1, 7.2.0 etc., to the version 7.5.2 provides access to new features and capabilities, updated technology components, and fixes for known bugs and security vulnerabilities.

The purpose of this RSA Knowledgebase Article is to describe the guidelines and resources, including known issues/remediation, to help plan a successful upgrade from older versions to SecurID Governance & Lifecycle 7.5.2.

Note: The original GA build of SecurID Governance & Lifecycle 7.5.2 was replaced in June 2022 with SecurID Governance & Lifecycle 7.5.2 P03 full installer. Refer to the following product advisory for more details:
Urgent SecurID Governance and Lifecycle Product Advisory – Request Activities Task Information Missing after Migration
Resolution
When planning to upgrade your SecurID Governance & Lifecycle deployment to the latest version, it may be a good opportunity to review your Identity Governance and Administration (IGA) business requirements and consider updating approaches to meet those requirements based on the new features and capabilities introduced in the latest version of the product.  Listed below are some guidelines and resources to help you plan a successful upgrade to SecurID Governance & Lifecycle 7.5.2.

IMPORTANT:  Ensure that a full backup of your existing SecurID Governance & Lifecycle deployment has been taken and verified before proceeding with the upgrade.
 

Product Documentation for Upgrades:

The primary reference for upgrading SecurID Governance & Lifecycle is the Upgrade and Migration Guide. Additional product guides may be referenced for detailed steps depending on the deployment scenarios.  

Recommended Practices for Upgrades:

The following Recommended Practices document provides guidance on the various upgrade options and choices/decisions to be made during the upgrade planning: Note:  Although the above document references an older version, the concepts/approaches in general also apply to SecurID Governance & Lifecyle 7.5.2.
 

Known Issues:

The following known issues require workarounds/remediation prior to and/or immediately after the migration part of the upgrade process:
 
DESCRIPTIONREMEDIATION
A new installation or an upgrade of software bundle deployment, using a remote database, to 7.5.2 P03 fails with error: Could not find necessary package adoptjdk_8u292b10.tar.gzRefer to the KB article 000067960 for a workaround.
BSAFE crypto libraries embedded in the SecurID Governance & Lifecycle product were updated which require IBM WebSphere Application Server based deployments to use IBM JDK 1.8.0_281 or later.IBM JDK version must be 1.8.0_281 or later when SecurID Governance & Lifecyle 7.5.2 P03 is deployed on IBM WebSphere Application Server.  Refer to the SecurID Governance & Lifecycle 7.5.2 P03 release notes for more details.
When upgrading from a previous version to SecurID Governance & Lifecycle 7.5.2, manual steps may be required to create a new AVCSUSER schema in the database.Refer to the SecurID Governance & Lifecycle 7.5.2 Upgrade and Migration Guide for steps on creating the new AVCSUSER schema in the database.  The AVCSUSER schema is required for a new feature SQL Utility introduced in version 7.5.2.
ACM-102799.sql script stalls for a very long time during migration when WP_USER_DATA table contains very large number of rowsRefer to the KB article 000067872.  Contact RSA Customer Support for assistance (reference: ACM-114260).
ACM-108053.sql script stalls for a very long time during migration when WP_USER_DATA table contains very large number of rows (e.g., 100M)Contact RSA Customer Support to engage Engineering team for a workaround specific to your environment (reference: ACM-111896).
ACM-97300.sql script stall for a very long time during migrationContact RSA Customer Support to engage Engineering team for a workaround specific to your environment (reference: ACM-113948).
ACM-86871.sql script stalls for a very long time during migration when T_AV_APPLICATION_LOG table contains very large number of rows (e.g., 50M)Contact RSA Customer Support to engage Engineering team for a workaround (reference: ACM-111395, ACM-113756).

 

Related Articles

Trending Articles

Don't see what you're looking for?