What is changing
TimeEdit already enforces TLS 1.2 or newer, and this remains unchanged.
With this update, we are tightening the set of allowed cipher suites (encryption methods within TLS) on our load balancers. We are moving to a more restricted cipher policy, which excludes weaker cipher suites that are being phased out according to industry best practices.
Supported cipher suites
After this change, the following cipher suites will be supported:
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Why we are doing this
This change improves transport security and aligns with current security recommendations and customer expectations. It reduces exposure to cryptographic weaknesses in outdated cipher suites.Impact
Most clients and integrations will not be affected.
Only very old clients or libraries that rely on deprecated cipher suites may experience connection issues.
Action required
No action is required if your systems support modern TLS configurations (TLS 1.2+ with up-to-date cipher support). If you maintain custom integrations, ensure your TLS libraries are up to date.