Auth0 End-of-Life Rollout for Weak TLS 1.2 Cipher Suites

Overview

Auth0 is deprecating weak TLS 1.2 cipher suites across service endpoints, including canonical and custom domains, as part of a 2026 security alignment with current industry best practices. The removal applies to public cloud, private cloud, and supporting services, with separate schedules and processes for each environment type. The dates and times listed below are subject to change. Updating client systems to use supported TLS configurations, or configuring a reverse proxy custom domain for compatibility scenarios, resolves the issue.

Applies To

  • Auth0
  • End of Life (EOL)
  • Networking
  • TLS 1.2 Ciphers

Cause

Auth0 stopped supporting specific TLS 1.2 cipher suites that no longer meet security standards as part of a 2026 change to align with current industry best practices and ensure a secure, reliable service. On December 10, 2025, Auth0 announced the deprecation of specific TLS ciphers; the original announcement is available in the respective Dashboard and Support Center notification.

Solution

How Are Public Cloud Environments Affected?

Auth0 performs a series of brownout tests in public cloud environments in which the service rejects TLS requests using weak ciphers for a defined time window, then restores previous behavior. Multiple rounds of testing aim to reduce the impact on non-compliant systems.

Review the public cloud brownout and removal schedule:

  • June 16, 2026 — 1-hour duration test with the following environment-specific start times:
    • 14:00 UTC — JP-1, AU-1, UK-1, EU-1, and EU-2
    • 18:00 UTC — US-3, US-4, and US-5
    • 20:00 UTC — US-1
  • June 23, 2026 — 4-hour duration test with the following environment-specific start times:
    • 14:00 UTC — JP-1, AU-1, UK-1, EU-1, and EU-2
    • 18:00 UTC — US-1, US-3, US-4, and US-5
  • June 30, 2026 — 8-hour duration test starting at 14:00 UTC for all public cloud environments
  • July 7, 2026 — Permanent removal starting at 14:00 UTC for all public cloud environments

How Are Private Cloud Environments Affected?

Auth0 deploys the change to private cloud environments in two separate stages: the first applies to development environments, specifically those without a guaranteed SLA, and the second applies to all remaining environments. Each stage is deployed according to the respective deployment window and release channel.

Review the planned private cloud rollout start dates:

  • June 16, 2026 — Private cloud development (non-SLA) environments
  • July 21, 2026 — Remaining private cloud environments

Supporting Services and Applications Deprecation Timeline

On September 1, 2026, supporting services — including Auth0 CDN endpoints, the public cloud Dashboard, Team Accounts, and Marketplace — stop supporting the deprecated TLS ciphers.

Updating Client Systems to Use Supported TLS Configurations

Update client systems that make network requests to Auth0 endpoints to use supported TLS configurations.

For use cases that require maintaining compatibility with older systems, set up a self-managed certificate custom domain and configure the reverse proxy to support discontinued TLS cipher suites for inbound connections. Ensure requests from the proxy to Auth0 use supported ciphers.

Recommended content

No recommended content found...