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

Unable to enable U2F auth with Yubikey (400 Bad Request) #526

Closed
Slychocobo opened this issue Jul 7, 2019 · 1 comment
Closed

Unable to enable U2F auth with Yubikey (400 Bad Request) #526

Slychocobo opened this issue Jul 7, 2019 · 1 comment

Comments

@Slychocobo
Copy link

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

@dani-garcia
Copy link
Owner

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.

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

No branches or pull requests

2 participants