FIDO U2F is not working with Google's OpenSK #896

New Issue

Closed

opened 2026-02-04 23:15:59 +03:00 by OVERLORD · 1 comment

OVERLORD commented 2026-02-04 23:15:59 +03:00

Owner

Copy Link

Originally created by @Fei1Yang on GitHub (Jan 8, 2021).

Subject of the issue

OpenSK won't be registered on the web vault.

Your environment

• Bitwarden_rs version: 1.18.0
• Install method: built from source
• Clients used: web vault
• Reverse proxy and version: nginx/1.19.6
• Version of mysql/postgresql: mysql
• Other relevant information:
  DOMAIN environment variable is already set.
  The OpenSK security key is working with my GitHub account so I don't think it's Google's fault.

Steps to reproduce

1. Open FIDO U2F registration page.
2. Fill the name and click "Read key".
3. Click the button on my key.

Expected behaviour

Web vault returns the error message "There was a problem reading the security key. Try again.".

Actual behaviour

OpenSK should be registered as a U2F security key.

Relevant logs

listening for key... u2f.js:702
Extension JS API Version:  1.1 two-factor-u2f.component.ts:138
error: 5 two-factor-u2f.component.ts:138

Originally created by @Fei1Yang on GitHub (Jan 8, 2021). ### Subject of the issue OpenSK won't be registered on the web vault. ### Your environment * Bitwarden_rs version: 1.18.0 * Install method: built from source * Clients used: web vault * Reverse proxy and version: nginx/1.19.6 * Version of mysql/postgresql: mysql * Other relevant information: `DOMAIN` environment variable is already set. The OpenSK security key is working with my GitHub account so I don't think it's Google's fault. ### Steps to reproduce 1. Open FIDO U2F registration page. 2. Fill the name and click "Read key". 3. Click the button on my key. ### Expected behaviour Web vault returns the error message "There was a problem reading the security key. Try again.". ### Actual behaviour OpenSK should be registered as a U2F security key. ### Relevant logs ``` listening for key... u2f.js:702 Extension JS API Version: 1.1 two-factor-u2f.component.ts:138 error: 5 two-factor-u2f.component.ts:138 ```

OVERLORD closed this issue 2026-02-04 23:16:00 +03:00

OVERLORD commented 2026-02-04 23:16:07 +03:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Jan 30, 2021):

I think error 5 means that either there's no https or the domain doesn't match. Please check those items first

@BlackDex commented on GitHub (Jan 30, 2021): I think error 5 means that either there's no https or the domain doesn't match. Please check those items first

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#896