AFX Server fails to start and unable to create a new AFX Server on WebSphere in RSA Identity Governance & Lifecycle

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
Platform: WebSphere
 

After upgrading or migrating from an earlier version of RSA Identity Governance & Lifecycle on WebSphere, AFX fails to start. An attempt to create a new AFX server also fails. This issue is unique to WebSphere installations.

The following error is logged in the aveksaserver.log file:
 
Note the aveksaServer.log file on WebSphere may be found in a directory similar to the following (where the specific node name would be different), /home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa.ear/aveksa.war/log. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
 

This is a known issue reported in engineering ticket ACM-103785.

This issue occurs when attempting to parse self-signed certificates generated on an older version of RSA Identity Governance & Lifecycle. Parsing these certificates leads to a call to a deprecated method in the bouncycastle crypto library.
 

This issue is being investigated by the Engineering team in order to provide a permanent resolution in a future release.
 

This issue may be resolved by generating new self-signed certificates. This generates certificates to replace legacy certificates that may have deprecated certificate attributes. AFX will have to be redeployed after this change.  

1. Generate new certificates.

2. Redeploy AFX.

 

Also refer to the following RSA Knowledge Base Article for additional changes that may be required for self-signed certificates with later Java versions.

000038503 -- AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0.241) or later in RSA Identity Governance & Lifecycle.