EEM Token EE_Exception is generated after upgrading PAM 4.4 to CP03

Products

• CA Process Automation Base

Issue/Introduction

While the USMcertfile.p12 file, created during standard patch installation, functions correctly in the CP02 environment, it fails in CP03.

c2o.log message:

Failed to evaluate pre-execution.

Failed to execute code:
load(Process.GblDSVals.JSCommonFunctions);

Process.ProcessStep__ = "Attempt Login";
if(isFIPSMode()=="true")
{
    logEvent(1,"CUSTOM","EEM is in fips mode");
    Process.Token__=getEEMArtifactToken(Process.SLCM_Cert_Path__, Process.SLCM_Key_Path__);
}
else
{
    logEvent(1,"CUSTOM","EEM is in non fips mode");
    Process.Token__=getEEMArtifactToken(Process.SLCM_Cert_Path__, Process.SLCM_Cert_Pass__);
}
CommonPreExec( Process.ProcessStep__ );

 -- Error occurred while generating EEM Token EE_EXCEPTION Exception (c2ojslib.js#1)

 

Environment

Release: 4.4 CP03

Component: Process Automation

Cause

The potential root cause is, when generating the p12 file, the process uses the safex.exe and it's always generated in a way that 
it's compatible with JDK 8 only. However, the process works correctly as intended when using the PAM 12 file generated with JDK 11, except for OpenJDK.

Resolution

The updated `c2ocore-snapshot.jar` and `c2oserver-snapshot.jar` files fixed safex.exe generated USMcertfile.p12 file issue, enabling P12 file generated via Java compatible with both OpenJDK 11 and Oracle JDK 11. Contact support for these JAR files if you encounter similar problems.

Additional Information

For PAM and SDM integration issue concerning the EEM certificate, please refer to KB Article ID: 378862