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

U2F UX issues #640

Closed
klizhentas opened this issue Dec 13, 2016 · 9 comments · Fixed by #903
Closed

U2F UX issues #640

klizhentas opened this issue Dec 13, 2016 · 9 comments · Fixed by #903
Assignees
Milestone

Comments

@klizhentas
Copy link
Contributor

Description

Here's a list of UI/UX issues I've encountered while using U2F:

  • When U2F error happens on the client, we see:
U2F Error: BAD_REQUEST

Error message. We should convert it to more human readable format.

  • Improve U2F information messages

When signing up or using u2f it's not clear that you have to press the button even following the instructions.

  • Too Many buttons

Now it's too many various login buttons everywhere. Rethink sign-in flow a bit especially when using U2F.

@markojak
Copy link

Yeah I have this problem as well - In fact I can't even get U2F to work with Teleport for sign-in
Created a new user and when signing up and selecting U2F it just says BAD_REQUEST

Have tried using two different Yubikeys but no matter the order can't complete the sign up process...

@klizhentas
Copy link
Contributor Author

@marchofreason what's your browser? U2F is only supported by Chrome or Opera at the moment are you using these?

@markojak
Copy link

markojak commented Jan 1, 2017

@klizhentas Sorry didn't mention this but yes I did try this with Google Chrome. Need me to send you any logs / developer console output?

Using the latest release from the binaries here:
v1.3.1

@klizhentas
Copy link
Contributor Author

@marchofreason can you send me your teleport config with U2F section. Just make sure to remove all secrets there. What's the domain name address you are accessing it from?

@markojak
Copy link

markojak commented Jan 2, 2017

@klizhentas I'm sorry the issue seems to have been that I had the configuration wrong. Auth and proxy server were the same so all I did was set U2F to enabled. Nothing further.

All working fine now!

    u2f:
      enabled: "yes"

Previously was:

    u2f:
      enabled: "yes"
      app_id: https://hostname.authserver.com:3080/appid.js
      facets:
      - https://hostname.authserver.com:3080

@klizhentas
Copy link
Contributor Author

@marchofreason awesome, glad to hear that

@kontsevoy
Copy link
Contributor

@klizhentas what are we doing with this one?

@klizhentas
Copy link
Contributor Author

@kontsevoy Ideally @alex-kovoy will handle the error on the UI and show something like:

Please check your U2F token settings, make sure it is plugged in and you are using supported browser

@klizhentas
Copy link
Contributor Author

and then we can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants