// AI Platform Drift

New Cloudflare AI Gateways require authentication, cannot be disabled

Cloudflare developer changelog · published 2026-11-11 05:27 UTC
ACTION NEEDED MIGRATE APISECURITY
WHAT CHANGEDCloudflare AI Gateway now enforces authentication on all newly created gateways as of 3 November 2026. The authentication field defaults to true and cannot be set to false; attempting to do so returns HTTP 400. Once authentication is enabled on any gateway, it cannot be turned off through the dashboard or API. Existing gateways with authentication disabled are grandfathered and can continue operating without it.
WHY IT MATTERSNew gateway deployments will reject unauthenticated requests immediately. Any existing gateway where you enable authentication becomes permanently locked in that state, preventing rollback if clients are not ready. HTTP clients must be configured with valid Cloudflare API tokens before authentication is turned on, or all requests will fail.
WHAT TO DOIf creating new AI Gateways after 3 November 2026, configure HTTP clients to send valid Cloudflare API tokens before deployment. For existing gateways, do not enable authentication until all clients are configured with tokens. Workers bindings remain pre-authenticated and require no change. See Cloudflare's AI Gateway authentication documentation for supported authorization headers.
ACT-BY DATE PASSED — this item's act-by date, 2026-11-03, is before this page was generated 2026-11-21 (UTC). Check the primary source before acting on it.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## AI Gateway - New AI Gateways require authentication
+https://developers.cloudflare.com/changelog/post/2026-11-03-required-authentication/
+Tue, 03 Nov 2026 00:00:00 GMT
+
+New AI Gateways now require authentication to prevent unauthorized requests. Once authentication is on, you cannot turn it off through the dashboard or API.
+When you create a new AI Gateway through the API, authentication is on by default. You can leave out the authentication field or set it to true. If you set it to false, the API returns HTTP 400.
+When you update an existing gateway, leaving out authentication keeps its current setting. If you try to turn off authentication after it is on, the API returns HTTP 400.
+Existing gateways with authentication turned off can continue without it. You can turn it on in your gateway settings or include authentication: true in a gateway update request:
+{
+"authentication": true
+}
+Before turning authentication on, configure HTTP clients to send a valid Cloudflare API token. Requests through Workers bindings remain pre-authenticated.
+For setup instructions and supported authorization headers, refer to AI Gateway authentication.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew AI Gateways enforce mandatory authentication with irreversible enforcement and breaking API constraints.
signalsfuture date: 2026-11-03 · breaking API change: new gateways require authentication by default · API behavior change: authentication field cannot be set to false on new gateways (HTTP 400) · irreversible state change: authentication cannot be turned off once enabled · authentication/security requirement imposed · existing gateways grandfathered but new ones locked
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)