Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EW: Starting then cancelling "verify with another device" should not allow user into the app #29230

Open
Tracked by #2700
mxandreas opened this issue Feb 7, 2025 · 0 comments
Labels
A-E2EE-SAS-Verification A-Login O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect T-User Story Team: Crypto

Comments

@mxandreas
Copy link

mxandreas commented Feb 7, 2025

Problem

As we make device verification mandatory, the users should not be allowed anymore into the app before they successfully verify their device. However, the current implementation on EW has not considered that when user chooses the option to verify with another device, they also instantly get into the app. Instead, the verification with another device should be carried out successfully before the user gets into the app.

Designs

  • The start of device verification flow when not logged in.

Note that besides showing the device verification outside of the app, the designs of the steps are also modernized. This design upgrade is desired, however it is acceptable if the old designs are used when the copy is aligned to the new designs.

@andybalaam andybalaam changed the title EW: Verifying with another device should not allow user into the app EW: Starting then cancelling "verify with another device" should not allow user into the app Feb 10, 2025
@richvdh richvdh transferred this issue from element-hq/element-meta Feb 10, 2025
@dosubot dosubot bot added A-E2EE-SAS-Verification A-Login O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect labels Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE-SAS-Verification A-Login O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect T-User Story Team: Crypto
Projects
None yet
Development

No branches or pull requests

1 participant