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
It's been pointed out to me that it would be a nice default for regular users to have backup codes be automatically generated and showed when activating any other method of 2FA.
It can be dangerous to only activate one 2FA method (decent risk of locking yourselsf out), so we should automatically create the backup codes and show them to the user and prompt them to copy them and keep them safe.
It is possible that not having backup codes or having only one 2FA method is what you really want, (hence my mention of regular users), but in this case you can either remove the backup codes method after or simply not make note of the backup codes.
The text was updated successfully, but these errors were encountered:
Hi there, any news on this? It could really benefit regular users and help establish good security workflows for organisations wanting to use 2FA on Wordpress.
Thanks!
I think having the Backup Verification Codes option as a selectable 2FA method is wrong. It should be moved out of the 2FA table and displayed similar to the Security Keys section outside the table.
If a 2FA option is selected, but the Backup Verification Codes have not been generated yet, a warning should be displayed.
It's been pointed out to me that it would be a nice default for regular users to have backup codes be automatically generated and showed when activating any other method of 2FA.
It can be dangerous to only activate one 2FA method (decent risk of locking yourselsf out), so we should automatically create the backup codes and show them to the user and prompt them to copy them and keep them safe.
It is possible that not having backup codes or having only one 2FA method is what you really want, (hence my mention of regular users), but in this case you can either remove the backup codes method after or simply not make note of the backup codes.
The text was updated successfully, but these errors were encountered: