Can an upgraded RSA SecurID Access Identity Router be rolled back to a previous version?
Originally Published: 2017-01-10
Article Number
Applies To
RSA Product/Service Type: Identity Router
Issue
Resolution
In the unlikely occurrence that an IDR version upgrade fails, download the current image from the admin console, open the VMware console to assign IPs, and go to the IDR Setup Console to register the IDR.
If any HTTP Federated (HFED) applications are being used and the IDR is a member of a cluster then user keychains will automatically be synced from an existing cluster member once the new IDR is active. If this is a single IDR system then restore the keychains from backup as described in the article on how to Restore a Backup for a Single Cluster.
Please see Chapter 5 (Installing and Configuring the Identity Router) of the RSA SecurID Access SSO Agent Setup and Configuration Guide, for more information on deploying a replacement IDR.
Notes
Related Articles
Attribute Change Rule reverts to a previous version after making changes in RSA Identity Governance & Lifecycle Number of Views Can the application be upgraded when there are active Reviews in RSA Identity Governance & Lifecycle? Number of Views Important information on upgrading to Sentry CA 3.7 from a previous version. Number of Views How to upgrade to Sentry CA 3.6 from a previous version of Sentry CA. Number of Views ServiceNow collectors are failing on an upgraded IBM WebSphere (WAS) server in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?
