Data Protection Advisor: "Request History" report generates Error 500

When executing the "Request History" report in DPA version 19.11, the following error is displayed:

• Error 500

Additionally, the following entry may appear in the server.log:

• 2024-09-17 13:45:47,495 ERROR [com.emc.dpa.reportengine.ComplexReportItem] (ReportEngineMessageListener #3:Request History:8bcb8628-7d93-42af-b09c-6d2a890304c1) Input returned error Unable to obtain data from remote plugin 'Request History'. Error message: Inbound closed before receiving peer's close_notify: possible truncation attack?

Example:

The issue is caused by incompatible or unsupported cipher suites used during secure communication with the "Request History" plugin. This results in the connection being prematurely closed, triggering an Error 500.

The following workaround steps can be applied.

1. Make a copy of the existing standalone.xml "<install dir>\EMC\DPA\services\standalone\configuration" and call it standalone_bkup.xml for example.

2. Update the original standalone.xml file and replace the cipher list, so that it looks as follows:

   enabled-cipher-suites="TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384"

3. The DPA services must be stopped and started in the following sequence:

   • Stop the application server and agent;
   • Stop the datastore and agent;
   • Start the datastore and agent;
   • Start the application server and agent.