Previous versions of CA Process Automation use self-signed jars within the Java Web start applications for agent and orchestrator installation. After the availability of JRE7u51/JDK7u51, Oracle escalated the javaws/JNLP security settings.
Symptom:
Due to the default JVM security settings, applets, and web start applications that are self-signed or use self-signed jars fail to start.
Solution:
To address the issue, CA Process Automation 04.2.01 Orchestrator and Agent components now only use CA-signed jars.
Note: If an agent uses JDK6, disable FIPS 140 compliance on all orchestrators (including each node of a clustered orchestrator). To disable FIPS 140 compliance on all orchestrators, set the pam.fips.mode.enabled parameter to “false” in the OasisConfig.properties file and restart the orchestrator.
|
Copyright © 2014 CA.
All rights reserved.
|
|