discourse/app
Krzysztof Kotlarek 4db5525d25
FIX: do not lock account if backup codes are available (#18982)
Currently, we have available three 2fa methods:
- Token-Based Authenticators
- Physical Security Keys
- Two-Factor Backup Codes

If the first two are deleted, user lose visibility of their backup codes, which suggests that 2fa is disabled.

However, when they try to authenticate, the account is locked, and they have to ask admin to fix that problem.

This PR is fixing the issue. User still sees backup codes in their panel and can use them to authenticate.

In next PR, I will improve UI to clearly notify the user when 2fa is fully disabled and when it is still active.
2022-11-11 13:00:06 +11:00
..
assets FIX: do not lock account if backup codes are available (#18982) 2022-11-11 13:00:06 +11:00
controllers FIX: do not preload topic list for new topic/message routes (#18959) 2022-11-09 20:57:42 +05:30
helpers Meta topic: https://meta.discourse.org/t/meta-theme-color-is-not-respecting-current-color-scheme/239815 (#18832) 2022-11-07 10:06:26 +03:00
jobs DEV: Quote values when constructing SQL (#18827) 2022-11-01 14:05:13 -05:00
mailers FEATURE: Custom unsubscribe options (#17090) 2022-06-21 15:49:47 -03:00
models FIX: do not lock account if backup codes are available (#18982) 2022-11-11 13:00:06 +11:00
serializers FIX: do not lock account if backup codes are available (#18982) 2022-11-11 13:00:06 +11:00
services FEATURE: Rename onboarding popups to user tips (#18826) 2022-11-09 20:20:34 +02:00
views UX: better password reset error page (#18970) 2022-11-10 17:48:25 +05:30