Updated: CA - PROACTIVE NOTIFICATION - EHCON - ADVISORY - CEHCON-100301

Document created by Bob_Keville Employee on Oct 4, 2016Last modified by Bob_Keville Employee on Dec 17, 2016
Version 4Show Document
  • View in full screen mode

This is an update to the original notice regarding the Java certificate expiration including affected versions and unaffected versions. The affected versions expanded to include 6.3.2.12 and the non-affected releases has also been expanded. Please see below for more detail.

 

Summary:

The Java certificate included in the CA eHealth 6.3.2.12 and earlier releases is set to expire on October 16, 2016. We have extensively tested this issue with eHealth, and found that only the Live Health applications: Live Exceptions, Live Status and Live Trend, along with Live Reporting, are affected.  Importantly, the core eHealth product (eHealth polling and reporting other than Live Reporting) and its supporting components and interfaces will not be affected by this Java certificate expiration.

 

Problem:

The Java certificate included in certain versions of CA eHealth expires on October 16, 2016.

 

Affected Releases:

CA eHealth releases 6.3.2.12, 6.3.2.11, 6.3.2.10, 6.3.2.9, 6.3.2.8, 6.3.2.7, 6.3.2.6, 6.3.2.5, 6.3.2.4, 6.3.2.3, 6.3.2.2, 6.3.2.1

 

Non-Affected Releases:

CA eHealth releases 6.3.2.13, 6.3.2.0, 6.3.1, 6.3.1.x, 6.3.0, 6.3.0.x, 6.2.2, 6.2.2.x.

 

Impact:

When attempting to launch one of the Live components on Windows clients that are running Java, the user will be challenged with a pop-up message that states that the certificate has expired.

               

Solution:

A hot-fix is available by request from CA Technical Support. Please contact CA Technical Support to request the hot-fix. Please have the OS and eHealth version readily available. Alternatively, as a workaround you can add your eHealth server info to the Java Exception Site List.

4 people found this helpful

Attachments

    Outcomes