Monitoring - Our engineering team has been investigating reports of SSL handshake errors when making API queries to Salsify from Java clients.
As part of the mandatory refresh of our SSL certificates, some customers may be affected by a change that Amazon, as our certificate provider, has made in their practice as a certificate authority.
On 2/14, Amazon updated the SSL cert for *.salsify.com. Amazon has stopped cross-signing their certs with Starfield Class 2, operated by GoDaddy. As a result, clients which relied on that trust relationship will no longer be able to complete the SSL handshake with https://app.salsify.com. To resolve this, you must either:
1. Update your application's list of trusted root CAs to include Amazon's Root CA 1 certificate, using the certificate found here: https://www.amazontrust.com/repository/
2. Update your application to run on a runtime which already supports Amazon's Root CA 1 certificate.
In particular, Java runtimes prior to Java 9 (except Java 8 Update 25 or later and Java 7 Update 75 or later) would need to be updated to a newer version of Java or have their list of trusted root CA's updated.
Resolved -
The platform has returned to a stable state. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
Feb 13, 12:18 EST
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 13, 08:04 EST
Investigating -
We are currently investigating this issue.
Feb 13, 06:27 EST
Monitoring -
The Salsify Application is back to normal. We will continue to observe performance closely.
Feb 13, 04:23 EST
Investigating -
We are currently investigating this issue.
Feb 13, 03:39 EST
Identified -
The issue has been identified and a fix is being implemented.
Feb 13, 03:31 EST
Investigating -
Our engineering team has identified an issue causing slowness across multiple areas of the Salsify Application.
We are investigating this behaviour with urgency and will provide an update as soon as possible.
Resolved -
We have discovered missing data within the EC Loads and Customer Data Feeds.
Our engineering team found and fixed a storage misconfiguration that was preventing logs necessary for downstream metrics from being delivered from the Content Distribution Network for Enhanced Content.
The impact of the missing data is the following for Legacy and Advance in-between January 28, 2025 & February 7, 2025
For Legacy: EC Analytics will be missing Impressions data for impacted window.
For Advance: All charts on the EC -> Analytics -> Impressions tab will reflect this missing data.
Customer data feeds will also be missing EC load events during the impacted window.