000037805 - Request Entity Too Large error when upgrading from RSA Authentication Manager 8.3 patch 6 to 8.4

According to the documentation, if you're upgrading RSA Authentication Manager from 8.3 to 8.4 while using the browser as the update source, you have to first upgrade to 8.3 patch 4 or patch 6 to be able to continue upgrading to 8.4. 

However, even with the patch installed when trying to apply the 8.4 update, the following error is received:

Error 413--Request Entity Too Large

1. Login to the Operations Console
2. Navigate to Maintenance > Update & Rollback.
3. Click Configure Update Source.
4. Select another update source from the available options (NFS, Windows Share, DVD/CD)
5. According to the selected update source if additional configuration is needed, add them.
6. Click Save.

1. Launch an SSH client, such as PuTTY.
2. Login to the primary Authentication Manager server as rsaadmin and enter the operating system password.

Note that during Quick Setup another user name may have been selected. Use that user name to login.

3. Navigate to /opt/rsa/am/server/config/.
4. Take a backup of the configuration file:

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

5. Open the config.xml using a text editor like vim:

vim /opt/rsa/am/server/config/config.xml

6. Find the entry for <max-post-size>, shown in bold below:

<web-server>
  <name>AdminServer</name>
  <web-server-log>
    <name>AdminServer</name>
    <file-name>../../logs/AdminServer_access.log</file-name>
    <rotation-type>bySize</rotation-type>
    <file-count>5</file-count>
    <file-min-size>5120</file-min-size>
    <elf-fields>c-ip date time time-taken cs-method cs-uri sc-status bytes</elf-fields>
    <log-file-format>extended</log-file-format>
  </web-server-log>
  <post-timeout-secs>15</post-timeout-secs>
  <max-post-time-secs>3600</max-post-time-secs>
  <max-post-size>2000000000</max-post-size>
</web-server>

7. Press i to enter Insert mode.
8. Edit the <max-post-size> value to be 4000000000, instead of 2000000000:

<web-server>
  <name>AdminServer</name>
  <web-server-log>
    <name>AdminServer</name>
    <file-name>../../logs/AdminServer_access.log</file-name>
    <rotation-type>bySize</rotation-type>
    <file-count>5</file-count>
    <file-min-size>5120</file-min-size>
    <elf-fields>c-ip date time time-taken cs-method cs-uri sc-status bytes</elf-fields>
    <log-file-format>extended</log-file-format>
  </web-server-log>
  <post-timeout-secs>15</post-timeout-secs>
  <max-post-time-secs>3600</max-post-time-secs>
  <max-post-size>4000000000</max-post-size>
</web-server>

9. Press Esc to exit from Insert mode
10. Type :wq! and press Enter to save and exit.
11. Take a backup of AdminServerWrapper.conf

cp /opt/rsa/am/server/wrapper/AdminServerWrapper.conf /opt/rsa/am/server/wrapper/AdminServerWrapper.conf.bak

12. Open AdminServerWrapper.conf using a text editor like vim:

vim /opt/rsa/am/server/wrapper/AdminServerWrapper.conf

13. Press <i> to enter Insert mode.
14. Add the following to the end of the file:

wrapper.java.additional.52=-Dweblogic.configuration.schemaValidationEnabled=false

The number 52 is a unique number to the additional configuration rule. It might need to be changed according to your version.

15. Press <Esc> to exit Insert mode.
16. Type :wq! and hit Enter to save and exit.
17. Restart the Authentication Manager services for the changes to take effect:

/opt/rsa/am/server/rsaserv restart all

18. Apply the update normally from your browser.

These changes are temporary. After upgrading to RSA Authentication Manager 8.4, the changes made above are reverted.