[GH-ISSUE #1251] FIDO U2F isn't shown while login #880

Closed
opened 2026-03-03 02:04:20 +03:00 by kerem · 3 comments
Owner

Originally created by @Gaojianli on GitHub (Dec 3, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1251

Subject of the issue

I can add FIDO device(yubikey) at console, but when I try to login, I can't find FIDO options.

Your environment

  • Bitwarden_rs version: 1.17
  • Install method: Docker image
  • Clients used: MS Edge 87.0.664.52 x64
  • Reverse proxy and version: nginx/1.19.0
  • Version of mysql/postgresql: 10.5.8-MariaDB-1:10.5.8+maria~focal
  • Other relevant information:

Steps to reproduce

  1. Add a U2F device at settings
  2. Logout and try to login again

Expected behaviour

I can choose any 2FA I configured, including U2F

Actual behaviour

I can't choose FIDO U2F
What I configured:
image

What I see:
image

Relevant logs

Request to /identity/connect/token returns a 400 Bad Request
image
Here is the response body:
image

Originally created by @Gaojianli on GitHub (Dec 3, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1251 <!-- # ### NOTE: Please update to the latest version of bitwarden_rs before reporting an issue! This saves you and us a lot of time and troubleshooting. See: https://github.com/dani-garcia/bitwarden_rs/issues/1180 # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS addresses and especially passwords, if necessary. --> ### Subject of the issue I can add FIDO device(yubikey) at console, but when I try to login, I can't find FIDO options. ### Your environment <!-- The version number, obtained from the logs or the admin diagnostics page --> <!-- Remember to check your issue on the latest version first! --> * Bitwarden_rs version: 1.17 <!-- How the server was installed: Docker image / package / built from source --> * Install method: Docker image * Clients used: MS Edge 87.0.664.52 x64 * Reverse proxy and version: nginx/1.19.0 * Version of mysql/postgresql: 10.5.8-MariaDB-1:10.5.8+maria~focal * Other relevant information: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> 1. Add a U2F device at settings 1. Logout and try to login again ### Expected behaviour I can choose any 2FA I configured, including U2F ### Actual behaviour I can't choose FIDO U2F What I configured: ![image](https://user-images.githubusercontent.com/19235246/100977272-b93d8b80-357b-11eb-9173-01f6eae72a5e.png) What I see: ![image](https://user-images.githubusercontent.com/19235246/100977243-adea6000-357b-11eb-9f34-ba538bdbd1a1.png) ### Relevant logs Request to `/identity/connect/token` returns a 400 Bad Request ![image](https://user-images.githubusercontent.com/19235246/100978122-e8083180-357c-11eb-8c84-744f4a68e7f9.png) Here is the response body: ![image](https://user-images.githubusercontent.com/19235246/100978066-d3c43480-357c-11eb-8caa-ebd51348b790.png)
kerem 2026-03-03 02:04:20 +03:00
Author
Owner

@BlackDex commented on GitHub (Dec 13, 2020):

I just tested it with a softu2f token and it all seems to work.
If you use any of the other 2FA ones, does it work?

Also, have you tried to remove and re-add the Fido U2F token?

Else we probably need a bit more information like logs etc...

Also, what happens if you create a new account and try to use it there?

<!-- gh-comment-id:744040667 --> @BlackDex commented on GitHub (Dec 13, 2020): I just tested it with a softu2f token and it all seems to work. If you use any of the other 2FA ones, does it work? Also, have you tried to remove and re-add the Fido U2F token? Else we probably need a bit more information like logs etc... Also, what happens if you create a new account and try to use it there?
Author
Owner

@Gaojianli commented on GitHub (Dec 16, 2020):

If you use any of the other 2FA ones, does it work?

Yes, all work except u2f

Also, have you tried to remove and re-add the Fido U2F token?

I tried it and it doesn't work.

Else we probably need a bit more information like logs etc...

Also, what happens if you create a new account and try to use it there?

A new user can use u2f normally

<!-- gh-comment-id:745899099 --> @Gaojianli commented on GitHub (Dec 16, 2020): > If you use any of the other 2FA ones, does it work? Yes, all work except u2f > Also, have you tried to remove and re-add the Fido U2F token? I tried it and it doesn't work. > Else we probably need a bit more information like logs etc... > Also, what happens if you create a new account and try to use it there? A new user can use u2f normally
Author
Owner

@Gaojianli commented on GitHub (Dec 16, 2020):

After stop, remove and restart the docker container, it finally works. Strange problem....

<!-- gh-comment-id:745926551 --> @Gaojianli commented on GitHub (Dec 16, 2020): After stop, remove and restart the docker container, it finally works. Strange problem....
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#880
No description provided.