mirror of
https://github.com/antonioribeiro/google2fa.git
synced 2026-04-25 08:05:49 +03:00
[GH-ISSUE #85] Backup Code #34
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/google2fa#34
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @plazari15 on GitHub (Sep 13, 2017).
Original GitHub issue: https://github.com/antonioribeiro/google2fa/issues/85
Have an way to create a Backup list of codes, like if my user don't have the cellphone next, he/her can use one code of the list.
@antonioribeiro commented on GitHub (Sep 19, 2017):
Not exactly the purpose of google2fa, maybe the case for a framework-specific package like google2fa-laravel.
But I just published a Backup/Recovery package, so it can help people, at least, generate the codes.
@tonybyng commented on GitHub (Nov 20, 2017):
Hi. Thanks for a great package. I had a similar question but have just had a look at the backup/recovery package. Am I right in thinking that we use the recovery package to generate a set of codes when a user is logged in, store them against the users account and modify the validate process to accept one of the generated codes instead of the 6 digit authenticator code?
@antonioribeiro commented on GitHub (Nov 20, 2017):
Yes, exactly, but
"generate a set of codes when a user register him/herself"
and not
"generate a set of codes when a user is logged in"
And I would also give a way for the user to regenerate them.