mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #772] 2FA authentication should not be enabled until we confirm user has configured google authenticator #472
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#472
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 @ElvisAns on GitHub (Sep 19, 2023).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/772
Originally assigned to: @Yannick243 on GitHub.
🗣 Suggestion
Let's consider the following scenario
Proposed solution
Before asking users to enter TOTP on login, we have to confirm they have google authenticator paired. Usually this is done by asking them to put the current TOPT during the configuration process and if match, we now enforce 2FA on next login.
@marclaporte commented on GitHub (Nov 4, 2023):
@ElvisAns Does the PR look good to you?
@ElvisAns commented on GitHub (Nov 5, 2023):
@marclaporte testing now, will share some feedback
@ElvisAns commented on GitHub (Nov 5, 2023):
@Yannick243 it looks good on my end
https://github.com/cypht-org/cypht/assets/35831811/d473311f-9334-4ad6-9189-d62834b7daba
@marclaporte what do you think about the flow above? User experience wise
@marclaporte commented on GitHub (Nov 5, 2023):
I refer to @johnsantosDev for UX :-)
@johnsantosDev commented on GitHub (Nov 5, 2023):
Let me give it a look Team
@johnsantosDev commented on GitHub (Nov 12, 2023):
Team, I tested this and the flow, works realy fine, just some very minor ui improvments related to the alignments.
I suggest to have the switch, the QR and the text "if you can't ..... " at the left column and the section starting with "the following backup codes can ... " at the right.
WDYT @Yannick243 ?
@Yannick243 commented on GitHub (Nov 13, 2023):
Hello @johnsantosDev,
I have refactor the UI like this, what do you think ?
@johnsantosDev commented on GitHub (Nov 13, 2023):
Perfect. Thanks @Yannick243
@Yannick243 commented on GitHub (Feb 2, 2024):
Hello @ElvisAns,
can this be closed as it has been merged ?
@ElvisAns commented on GitHub (Feb 6, 2024):
PR : https://github.com/cypht-org/cypht/pull/819