You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-03-04] [Domain control] [Release 3.1] - Bug: 2FA code validation errors on domain settings show RBR instead of error message only under the form input #82445
When a domain admin with 2FA enabled attempts to disable the "Force two-factor authentication" domain setting and enters an invalid 2FA code, the error (e.g., "Invalid code") is displayed both under the 2FA code form input and as a Red Brick Road (RBR) indicator in the domain members settings.
The expected behavior is:
2FA code form errors should only appear under the 2FA code form input as a form validation error without RBR in the domain settings
Domain-level 2FA settings errors should appear as RBR in the domain settings
This happens because all errors from ToggleTwoFactorAuthRequiredForDomain are currently routed to a single Onyx key (domainErrors_<domainAccountID>.setTwoFactorAuthRequiredError), which is read by both the 2FA toggle settings page and the 2FA form page.
Solution
The fix requires splitting the error routing so that 2FA code validation errors go to a new Onyx key, and updating the frontend form page to read from it. The same split applies to SetTwoFactorAuthExemptEmailForDomain command.
changed the title [-][Domain control] [Release 3.1] - Bug: 2FA code validation errors on domain settings show RBR instead of error message only under the form input[/-][+][Due for payment 2026-03-04] [Domain control] [Release 3.1] - Bug: 2FA code validation errors on domain settings show RBR instead of error message only under the form input[/+]on Feb 25, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.25-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
rayane-d commentedon Feb 13, 2026
Draft PRs:
rayane-d commentedon Feb 13, 2026
rayane-d commentedon Feb 17, 2026
Web-E PR is merged. pending deploy.
rayane-d commentedon Feb 19, 2026
Update:
rayane-d commentedon Feb 23, 2026
Updated: App PR merged, pending deploy
rayane-d commentedon Feb 24, 2026
closing for now
[-][Domain control] [Release 3.1] - Bug: 2FA code validation errors on domain settings show RBR instead of error message only under the form input[/-][+][Due for payment 2026-03-04] [Domain control] [Release 3.1] - Bug: 2FA code validation errors on domain settings show RBR instead of error message only under the form input[/+]melvin-bot commentedon Feb 25, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 25, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.25-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-04. 🎊
For reference, here are some details about the assignees on this issue: