feat: add too_many_attempts error to passwordless - #2700
Merged
Merged
Conversation
avamachado-okta
marked this pull request as draft
December 8, 2025 21:24
avamachado-okta
marked this pull request as ready for review
December 17, 2025 19:59
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2700 +/- ##
==========================================
+ Coverage 42.54% 43.52% +0.97%
==========================================
Files 120 120
Lines 3145 3180 +35
Branches 337 339 +2
==========================================
+ Hits 1338 1384 +46
+ Misses 1713 1701 -12
- Partials 94 95 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
1 similar comment
Contributor
ankita10119
approved these changes
Dec 19, 2025
Merged
ankita10119
added a commit
that referenced
this pull request
Jan 12, 2026
**Added** - feat: add too_many_attempts error to passwordless [\#2700](#2700) ([avamachado-okta](https://github.com/avamachado-okta)) **Changed** - Update: Upgrade Node.js from 18 to 22 [\#2711](#2711) ([ankita10119](https://github.com/ankita10119))
7 tasks
7 tasks
ankita10119
added a commit
that referenced
this pull request
Aug 17, 2026
…all locales (#2839) ### Changes Adds the too_many_attempts error message to the error.passwordless section in all 44 locale files, bringing v13 to parity with master. Also relaxes the i18n sanitizer test assertion from an exact string match to regex matchers, making it resilient to attribute ordering differences across sanitizer versions. No API or UI changes. ### References - #2700 - "feat: add too_many_attempts error to passwordless" ### Testing * [ ] This change adds unit test coverage * [ ] This change adds integration test coverage * [ ] This change has been tested on the latest version of the platform/language Existing i18n test suite passes. The sanitizer test (should sanitize the input and not allow for javascript to be passed through) was updated to verify attributes individually rather than asserting a fixed output string. ### Checklist * [ ] I have read the [Auth0 general contribution guidelines](https://github.com/auth0/open-source-template/blob/master/GENERAL-CONTRIBUTING.md) * [ ] I have read the [Auth0 Code of Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md) * [ ] All code quality tools/guidelines have been run/followed * [ ] All relevant assets have been compiled
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Add Brute-Force Protection
too_many_attemptserror to passwordless error mappings to support adding Brute-Force Protection topasswordless/startendpointReferences
https://auth0team.atlassian.net/browse/EUP-23
Testing
This was tested alongside changes to enforce Brute-Force Protection on the
passwordless/startendpoint behind a feature flag. The error is not currently emitted in this location.The current behavior without this change just shows generic error when Brute-Force Protection is enforced and the feature flag is enabled:
Checklist