TLS Handshake Failures on Legacy B2B Clients (IBM CIS & Let's Encrypt)

2026-08-30

Problem

An API pipeline began failing with HTTP 526 (Invalid SSL) errors on connections from a legacy enterprise client.

Symptoms

HTTP 526 (Invalid SSL) errors returned to the pipeline
The legacy B2B client (IBM Sterling / older Java runtime) connecting to the IBM CIS-fronted endpoint failed to establish a TLS handshake and dropped instantly
Modern browsers hitting the same endpoint were unaffected

Observed

The certificate served by IBM CIS at the time of failure was issued from Let's Encrypt's YE2 (ECDSA) intermediate
The legacy client's TLS stack lacks support for ECDSA cipher suites, so it could not negotiate the handshake

Root cause (working theory)

We believe IBM CIS changed its default managed-edge certificate to the YE2 (ECDSA) intermediate. This is our working theory based on observing the served certificate change in our own environment — we did not confirm this via IBM CIS's own change log or documentation, so we can't say whether this was a deliberate, vendor-wide default change or something scoped more narrowly to this endpoint.

Why the obvious fix failed

Importing the new YE2 root/intermediate into the legacy client's trust store did not fix the issue. Even once the CA was trusted, the client's underlying TLS stack still could not process ECDSA cipher suites at all — trust and cipher support are separate problems, and this fix only addressed the first one.

Fix

Uploaded a custom RSA (YR2) certificate and matching private key to the IBM CIS edge as an SNI custom certificate.

Verify

Confirmed CIS's dynamic fallback behavior: modern browsers still receive the faster ECDSA (YE2) cert, while the legacy IBM Sterling client now receives the RSA (YR2) cert instead. Handshakes from the legacy client succeeded after deployment.

Takeaway

Anyone running legacy B2B integrations through IBM CIS should audit which cipher/cert type is being served by default, since a provider-side change on the ECDSA/RSA default can silently break legacy clients. A hybrid RSA/ECDSA setup deployed proactively avoids this failure mode.