|Applies To||RSA Product Set: RSA Identity Governance and Lifecycle|
RSA Version/Condition: 7.0.1+
Product Name: AFX
|Issue||RSA Identity Governance and Lifecycle Access Fulfillment Express (AFX) fails to startup. In the console, under AFX Servers, the status shows as Not running.|
The following errors are logged in /home/oracle/AFX/esb/logs/esb.AFX-INIT.log:
2017-02-02 09:13:06.707 [INFO] org.mule.lifecycle.AbstractLifecycleManager:193 - Starting: 'connector.https.mule.default.dispatcher.697427580'. Object is: HttpsClientMessageDispatcher
The following errors are logged in /home/oracle/AFX/esb/logs/mule_ee.log:
ERROR 2017-02-02 09:13:07,030 [WrapperListener_start_runner] org.mule.module.launcher.DefaultArchiveDeployer:
|Cause||This issue may occur if the encrypted configuration data for the AFX server is encrypted with a different key than the system-wide encryption keys stored in /home/oracle/security. This may occur for a variety of reasons, including the following examples:|
The system-wide encryption keys were introduced in 7.0.1 and later versions.
|Resolution||Recover the Encryption Key from the master key storage directory as per the instructions on page 34 of the RSA Identity Governance and Lifecycle V7.0.1 Database Setup and Management Guide.|
|Workaround||If you elect not to recover the Encryption Key from the master key storage directory, then the AFX startup failure can be resolved by re-encrypting the AFX Default Truststore Password.|
Under the AFX > Servers menu,
This will ensure that the Default TrustStore is encrypted with the current keys.
NOTE: If you have imported any AFX connectors from another system you will have to edit each of the connectors and update any encrypted fields (passwords) by re-entering the password and saving the connector definition.