Access Manager 6.2.2 Manual Upgrade Needs Encrypted Config files Manually Reproduced
Originally Published: 2015-02-05
Last Modified: 2023-10-06
Article Number
Applies To
Encrypted server configuration files in version 6.2sp1 or prior
Issue
The Manual instructions fail to include the step of re-creating the encrypted configuration files if they were being used prior to upgrading to Access Manager 6.2 SP2
Cause
If the automated script fails, a manual upgrade can be done.
The automated script automatically re-creates the encrypted server configuration files.
The Manual instructions fail to include the step of re-creating the encrypted configuration files
Resolution
This is done by deleting the appropriate .enc file, for example aserver.enc
After deleting the encrypted server configuration file, follow the instructions in the RSA Access Manager 6.2 SP2 Server installation and Configuration Guide to create it again using cryptedit.
Related Articles
When is a wildcard certificate needed in RSA SecurID Access? 112Number of Views How to run the RSA AMBA utility without the need of input files? 38Number of Views Need to add HTML to a review email template in IMG/Aveksa 106Number of Views Does RSA Identity Governance and Lifecycle MAX_STRING_SIZE need to be modified from STANDARD to EXTENDED to accommodate st… 19Number of Views Need to wait until updating radius_connector.ini file after AM8.6 upgrades replica side 131Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog RSA Authentication Manager 8.9 Patches and Hotfixes Readme
Don't see what you're looking for?