• With a server running RSA Authentication Manager 8.3.0.5.0, when uploading the 8.4 update to the Operations Console via any browser, it processes for a few minutes then fails with the following error:

• After the error, the user is prompted for the RSA admin password.
• This leaves the system in a state where a reboot or restart of services fails.

I.  To get system operational again after failure

This modification has been approved by CE as a valid workaround to get the server running again.

1. Open an SSH session to the server.
2. Manually edit the /opt/rsa/am/server/config/config.xml.
3. Change any references in the file for 0.4.0 to 0.5.0.  See the Workaround section below for an easy way to edit the config.xml using the sed command.

Do not change items which may show 8.3.0.0.0, these you leave alone.

4. Restart services:

II.  To get Authentication Manager 8.4 to update from 8.3.0.5.0 successfully where it failed earlier on browser upload

1.  Update via hotfix

1. Obtain the hotfix zip file from AM-32518 or attached to this article.
2. Follow the instructions in the readme, as they may be updated. but the instructions are also written below.
3. There will be one jar file named ims-container-weblogic-8.3.0.5.0.jar, which replaces four copies of the jar file in four directories.
   1. Copy the hotfix jar file to /tmp.
   2. Create four .bak files:

3. Put in the new jar file in the following four locations:

4. Restart the Authentication Manager services:

5. If this is a primary, confirm that replication is normal.
6. Now upload 8.4 update via browser and it will succeed

2.  ^New Better solution from Engineering released 4 January 2019, no hotfix needed

1. Navigate to the /opt/rsa/am/server/pending directory.
2. Delete any config.xml files in he directory.  There should be one, which is the root cause of this problem.
3. Make sure all of the Authentication Manager services are stopped:

4. Edit the /opt/rsa/am/server/config/config.xml to correct the version numbers as shown in the Workaround section below.
5. Restart the Authentication Manager services:

6. If this is a primary, confirm that replication is normal.
7. Now upload 8.4 update via browser and it will succeed

Workaround to get the system functional after failure

1. Manually edit /opt/rsa/am/server/config/config.xml and change any references of 0.4.0 to 0.5.0.

config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/annex/8.3.0.4.0/annex-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/operations-console/8.3.0.4.0/operations-console-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/am-app/8.3.0.4.0/am-app-8.3.0.4.0.ear</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/am-radius-app/8.3.0.4.0/am-radius-app-8.3.0.4.0.ear</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/ims-authn-idp/8.3.0.4.0/ims-authn-idp-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/console-ims/8.3.0.4.0/console-ims-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/ctkip-ws/8.3.0.4.0/ctkip-ws-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/ucm-rba-war/8.3.0.4.0/ucm-rba-war-8.3.0.4.0.war</source-path>
config.xml:   <source-path>/opt/rsa/am/components/compile/com.rsa.am/ucm-rba-scm/8.3.0.4.0/ucm-rba-scm-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/console-selfservice/8.3.0.4.0/console-selfservice-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/console-selfservice-infocenter/8.3.0.4.0/console-selfservice-infocenter-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/console-infocenter/8.3.0.4.0/console-infocenter-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.am/console-shared-library/8.3.0.4.0/console-shared-library-8.3.0.4.0.war</source-path>
config.xml:    <source-path>/opt/rsa/am/components/compile/com.rsa.gtk/guitoolkit-shared-library/8.3.0.4.0/guitoolkit-shared-library-8.3.0.4.0.war</source-path>
 

Using stream editor (sed) to update the config.xml instead of line-by-line editing

1. Make a backup copy of config.xml

cp /opt/rsa/am/server/config/config.xml-bak

2. Navigate to /opt/rsa/am/server/config.
3. Run this sed command to replace all 8.3.0.4 to 8.3.0.5

sed -i -e 's/8\.3\.0\.4/8\.3\.0\.5/g' config.xml

4. Double check the config.xml for the changes:

fgrep 8.3.0. config.xml

The output should show all lines 8.3.0.5 and some 8.3.0.0.0

5. Restart services:

Workaround to upload 8.4 update via browser successfully on 8.3.0.5.0 system with earlier failure
 

• The old workaround is to attempt applying the the hotfix as documented in section 1 of the Resolution section above before trying the upgrade to 8.4 again.
• ^New Review the Engineering-approved workaround released on  4 January 2019, as documented in section 2 of the Resolution section above before trying the upgrade to 8.4 again.

Workaround to bypass this issue altogether