Skip to main content
Aug 25, 2025 9:43 AM UTC
Solved

1Password Firefox Extensions interferes with Hardware U2F keys on gitlab.com

Hi,

we use 1Password for Password management at work and use a Yubikey hardware key as second factor.

 

In the Firefox Browser: When using a yubikey (probably same issue with other u2f keys) as second login factor on gitlab.com when using firefox then the login fails with

 

 There was a problem communicating with your device. (InternalError).

In the console the following is written:

TypeError: CredentialsContainer.get: Missing required 'challenge' member of PublicKeyCredentialRequestOptions.
... from webauthn-listeners.js:5:2508

This only happens when the 1Password extension in firefox is also running (which is the case for me because I need it for my the Gitlab.com password).

 

There is already an issue for this on the firefox side: https://bugzilla.mozilla.org/show_bug.cgi?id=1982582 but it looks like it only happens when the 1Password firefox extension is also running so it looks like an error or interference with it. Other browsers like chrome do not have the same issue.

For me that happens on Linux but the firefox bug report is having the same issue on windows.

What is interesting is that for other websites like amazon aws console, the hardware key is working in combination with the 1Password extension running.

I know this is a tricky thing because it could be an issue either on gitlab.com, firefox or the 1Password extension but its weird that the bug is not happening if the 1Password firefox extension is not running.

Thank you for your help.

yookisiAnswer
Oct 14, 2025 12:42 PM UTC

Im not sure what fixed it but it is working now! Issue is resolved

3 replies

Aug 28, 2025 2:45 AM UTC

+1 I'm experiencing this on Firefox 142.0.1 (aarch64) on Mac OS 15.6.0 and 15.6.1 (24G90) accessing GitLab

yookisiAuthorAnswer
Oct 14, 2025 12:42 PM UTC

Im not sure what fixed it but it is working now! Issue is resolved

1P_Timothy
Community Manager
Community Manager
Oct 16, 2025 3:49 PM UTC

Thanks for the update! I'm glad to hear this is now working for you. If you encounter this again, or if there's anything we can help with, just let us know!