[GH-ISSUE #526] Unable to enable U2F auth with Yubikey (400 Bad Request) #332

New issue

Closed

opened 2026-03-03 01:28:04 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:28:04 +03:00

Owner

Originally created by @Slychocobo on GitHub (Jul 7, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/526

Trying to add U2F to an account, while browser reads the Security key, the process fails when attempting to save with "U2F Error"

Running latest docker-build of Bitwarden_rs.
Site is behind a nginx proxy (using proxy config provided in wiki)

Javascript console reports
zone.js:1152 PUT https://redacted.fqdn/api/two-factor/u2f 400 (Bad Request)

Server reports
[2019-07-07 19:09:52][bitwarden_rs::error][ERROR] U2fError.
,[2019-07-07 19:09:52][_][INFO] Matched: PUT /api/two-factor/u2f (activate_u2f_put)
,[2019-07-07 19:09:52][rocket::rocket][INFO] PUT /api/two-factor/u2f application/json; charset=utf-8:
,[CAUSE] NotTrustedAnchor

Checked app-id.json and it is reporting the correct URL/port

Originally created by @Slychocobo on GitHub (Jul 7, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/526 Trying to add U2F to an account, while browser reads the Security key, the process fails when attempting to save with "U2F Error" Running latest docker-build of Bitwarden_rs. Site is behind a nginx proxy (using proxy config provided in wiki) Javascript console reports zone.js:1152 PUT https://redacted.fqdn/api/two-factor/u2f 400 (Bad Request) Server reports [2019-07-07 19:09:52][bitwarden_rs::error][ERROR] U2fError. ,[2019-07-07 19:09:52][_][INFO] Matched: PUT /api/two-factor/u2f (activate_u2f_put) ,[2019-07-07 19:09:52][rocket::rocket][INFO] PUT /api/two-factor/u2f application/json; charset=utf-8: ,[CAUSE] NotTrustedAnchor Checked app-id.json and it is reporting the correct URL/port

kerem closed this issue

2026-03-03 01:28:04 +03:00

kerem commented

2026-03-03 01:28:05 +03:00

Author

Owner

@dani-garcia commented on GitHub (Jul 9, 2019):

This is probably the same error as #272 or #105, which means there's not much we can do at the moment. Some keys don't have the SubjectAltName field, (which isn't required for a U2F cert, so some keys don't have them) while the library used for reading them does expect the field to be there. Until those issues are fixed or another library appears there's nothing I can do.

@dani-garcia commented on GitHub (Jul 9, 2019): This is probably the same error as #272 or #105, which means there's not much we can do at the moment. Some keys don't have the SubjectAltName field, (which isn't required for a U2F cert, so some keys don't have them) while the library used for reading them does expect the field to be there. Until those issues are fixed or another library appears there's nothing I can do.