Archive

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

10-04-2016 12:34 PM

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.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

10-05-2016 12:16 PM

Thanks for the Update Bob.

10-05-2016 11:49 AM

Oops! Sorry Bob. I didn't look at that.

10-05-2016 11:40 AM

Hi Frank - please accept my apologies for the short notice. Once we understood we were affected our development team quickly developed and tested a hot-fix. Though not ideal we have tried to respond rapidly to head off any customer outages.

 

Thanks,

 

Bob

10-05-2016 11:36 AM

Hi Rajashekar - I've posted an update to the original letter above that should clarify the affected and non-affected releases. The 6.3.1.x releases are not affected by this.

 

Bob

10-05-2016 09:52 AM

Bob,

 

Any news on 6.3.1.x versions? Please let me know.

I tried to change date on my desktop to 17th October, 2016 and don't see any issues? But, need official confirmation on this.

10-05-2016 02:25 AM

Thank you for this information!

But:

Do  you think, 12 days are enough for us customers to react?

 

And for your information:

The Spectrum team knows since (at least) 6 months that their "Day X" is  on October 16.

And they have told it to us.

 

Regards, Frank

10-04-2016 01:29 PM

Hi Bob,

 

What about 6.3.1.x versions which are not listed? Will there be an impact? Please let me know.

 

 

Regards,

Rajashekar

Related Entries and Links

No Related Resource entered.