Access Manager 6.2.2 Manual Upgrade Needs Encrypted Config files Manually Reproduced
Originally Published: 2015-02-05
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? Number of Views Does RSA Identity Governance and Lifecycle MAX_STRING_SIZE need to be modified from STANDARD to EXTENDED to accommodate st… Number of Views What you need to do before you add new policies with Session Attributes - Spring Release Migration Number of Views Do Web Services need to be enabled if they are not being used in RSA Identity Governance & Lifecycle? Number of Views How to run the RSA AMBA utility without the need of input files? Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide "HTTP response error! Response code=401" when starting RSA Identity Governance and Lifecycle Access Fulfillment Express (A…
Don't see what you're looking for?
