-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
When connecting a new device, device verification does not start automatically #24490
Comments
I think this is what you're asking for @giomfo ... New log in: Verification requested: |
@giomfo I also wanted to add some clarifications...
|
Just to make sure there's no misunderstanding:
What's the actual user story here? |
Thanks @americanrefugee and @pmaier1, we agree with your suggestion. We will schedule the implementation of the suggested design.
|
Agree 👍
Please take into account that the verification dialog will automatically appear once a user starts the verification on a new device. I'm wondering what it is that you will change here after all. Is it just the button labels then? |
Yes, and the layout of the dialog |
Button labels are up to date. The new layout is still missing. |
Your use case
When a new session is detected the following dialog is displayed:

What would you like to do?
Start the verify device process automatically instead of navigating to the devices list in the application settings.
When the dialog appears, the first click should kick-off the process.
Note: Don't mix up with the incoming verification dialog:

Why would you like to do it?
How would you like to achieve it?
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: