Auth0 End-of-Life Rollout: Default Security Mode for Third-Party Applications
Last Updated:
Auth0 is changing the default security mode from permissive to strict when using the Management API to create third-party applications without specifying a third_party_security_mode value. This change is due to the behavior of defaulting to permissive being deprecated and reaching end of life (EOL) on October 23, 2026. The content below outlines the EOL rollout timeline, the availability of each security mode, and the actions required to adapt to the new default.
Rollout Transitions Tenants in Phases
The phase dates mark the beginning of each sequential rollout stage. Each phase may take several weeks, so tenants within the same phase may receive the change at different times. Updates will be posted here as the transition timeline is finalized.
| # | Start Date | Version | Scope |
|---|---|---|---|
| 1 | Nov 2, 2026 | 202645 | Force new behavior in development and staging tenants. |
| 2 | TBD | - | Force new behavior in all remaining tenants, including production. |
Auth0 applies the transition based on the tenant's environment tag when the rollout for that environment occurs. Changing a non-production tenant to production after its phase is deployed does not restore access to the deprecated behavior.
Security Modes for Third-Party Applications
Third-party applications, those owned and operated by an external organization that controls their deployment, holds their credentials, and determines their behavior, can behave according to one of the following security modes:
strict(enhanced security controls): Enforces OAuth 2.1 compliance. Supports only theauthorization_code(with mandatory PKCE) andrefresh_tokengrant types. Requires an explicit client grant to access any API, regardless of the API's own access policy.permissive(legacy): Preserves original behavior for backward compatibility in tenants that were using third-party applications before the introduction of enhanced security controls.
The security mode is determined during client application creation and cannot be changed afterward.
Permissive Security Mode Only Available in Tenants With Prior Usage
The permissive security mode is available only for subscriptions that had tenants with at least one third-party application configured before April 23, 2026. Subscriptions without prior third-party application usage only support the strict security mode and, as such, are unaffected by this change in defaults.
Note that applications created via the Auth0 Dashboard always use strict mode; the possibility to select the permissive mode in eligible tenants does not apply to the Auth0 Dashboard.
Impact on Existing Third-Party Applications
Existing third-party applications continue to work as before, since the change in defaults affects only the creation of new applications via the Management API. For eligible tenants, both modes can coexist, and customers can always explicitly choose either mode on a per-application basis via the Management API, both before and after the end-of-life rollout for the default behavior change.
Update Management API Client Creation Flows
Once a tenant transitions to the new default, creating a client via POST /api/v2/clients without specifying a third_party_security_mode value results in a strict third-party application rather than a permissive one.
Flows that require creating third-party applications with permissive-mode compatibility must include "third_party_security_mode": "permissive" in the request message sent to the client creation endpoint.
Dynamic Client Registration Uses a Separate Security Mode Setting
Dynamic Client Registration (DCR) is not affected by the change in the default behavior of the Management API client creation endpoint.
For tenants maintaining access to the permissive mode, DCR client creation is governed independently by the dynamic_client_registration_security_mode tenant setting, which is configurable via PATCH /api/v2/tenants/settings. Configure default API permissions before enabling strict mode for DCR, since DCR clients cannot access any API without them.
Why is Auth0 Making these Changes?
Auth0 introduced enhanced security controls for third-party applications to align with OAuth 2.1 best practices, providing explicit API authorization, mandatory PKCE, and a reduced attack surface for applications operated by external organizations. The change was first announced on April 30, 2026, via product notification.