- Auth0 now requires the "aud" claim in private‑key‑JWT client authentication to be a single JSON string containing the tenant’s issuer identifier.
- Providing an audience as a JSON array or as a URL string is deprecated and will be rejected in a future release.
- OIDC enterprise connections using Private Key JWT can also use the issuer identifier as the single‑string audience.
Audience Validation for Private Key JWT Client Authentication
Official Auth0 changelog summary with source attribution, release tags, and community reactions.
Track this Auth0 release note alongside related changelog updates, risky changes, and weekly digest signals from the developer community.
Verify the original release note
Every summary should remain traceable to the original changelog or release source.
Follow this in context
Turn this Auth0 release note into a weekly digest for the tools you actually use.
Create digestMore Auth0 changelog updates
Introduces early‑access Custom Rate Limits allowing per‑client or group throttling of Authentication API requests via API‑based self‑service configuration.
Introduces GA Flexible Password Policy replacing legacy settings with a unified `options.password_options` object for granular controls (composition, history, dictionary, profile data).
Custom signup/login fields and consent checkboxes now also apply to Social and Enterprise connections.