Our team has found the root cause: login field is type 'email' now. If our customers experience failing logins as a result - it was possible to login without '@' before - they can enable 'Requires Username' in the connection settings to properly configure the feature and fix the issue.
Posted Nov 26, 2024 - 12:25 UTC
Identified
On November 26, our Engineering team identified an issue which was impacting a subset of our customers who rely on username login flows without the use of '@' as part of their custom db configurations. We continue to work with impacted customers who may have been affected by this issue.
Posted Nov 26, 2024 - 11:56 UTC
This incident affected: Auth0 Europe (PROD) (User Authentication), Auth0 Australia (PROD) (User Authentication), Auth0 US (PROD) (User Authentication), Auth0 US-3 (PROD) (User Authentication), and Auth0 UK-1 (PROD) (User Authentication).