JourneyApps Product Team

Upcoming Change in Certificate Authorities for HTTPS Services: Some API clients may be affected.

AUTHOR: JourneyApps Product Team

7 February: This update is now complete and changes are in effect.

6 February: This update is currently in progress. Changes will only take effect on 7 or 8 February, with no downtime expected.

This notice details an upcoming change in the Certificate Authorities (CAs) for our HTTPS services, specifically relevant for clients connecting via our app backend API. Currently, our services use Let's Encrypt and GoDaddy as CAs. Starting early February, we will be introducing an additional CA.

Change Date: On 6 February 2024, we will add ZeroSSL as an additional CA. We won't immediately remove any of the existing CAs and so our services will be using a combination of Let's Encrypt, GoDaddy, and ZeroSSL from this date.

Impact on API Clients: Some API clients may be affected by this change, particularly those explicitly specifying CA certificates instead of using system defaults.

  • Action required: If you are currently explicitly specifying CA certificates in JourneyApps API clients, please ensure that you are additionally including the certificate bundle from ZeroSSL by 6 February 2024. Feel free to reach out to us if you need the bundle.

Impact on End Users: End users should not be affected by this change. The new ZeroSSL certificate will be recognized and trusted by all current devices.

Background for the Change: We're making this change because an intermediate certificate used by Let's Encrypt is expiring soon. To ensure compatibility with older clients (specifically Android 7.0 and below), we're transitioning some services to ZeroSSL.

Feel free to contact us if you have any questions or concerns about this upcoming change.

Powered by LaunchNotes