1password blocks my security key when passkey stored there *and* 1p

AlmoEnd
AlmoEnd
Community Member

Google | logout | sign in to Google with 1p extension enabled | click the icon for the security key (Yubikey 5 NFC) | No prompt for unlock code | Google returns "Something has gone wrong" | disable 1p browser extension | repeat from logout above | this time a popup asking me for the unlock code | success signing on to Google.

Therefore, I am assuming a bug in the software? I have dual boot so can try it in Windows 11 to see if same behavior.


1Password Version: 8.10.56
Extension Version: 8.10.56.28
OS Version: LMDE
Browser: Brave

Comments

  • AlmoEnd
    AlmoEnd
    Community Member
    edited January 2

    Windows behavior somewhat different from Debian 12. Here, I click the security key icon and browser asks for Pin (Windows PIN, not FIDO2 PIN), but there's another option "Try a different way" and it has a Security Key as an option. Then I'm asked for the Key's FIDO2 PIN. This is with 1P browser extension enabled or disabled. So it seems Linux is the problem for the 1P extension, although use of the key is kind of "buried" in the prompts, and I have to do about a 10-click/touch/entry process (touch the key, enter the FIDO2 PIN, touch key again). Wish it were simpler, and worked cross-platform better. Linux is my "daily driver" so I'd really like to see some acknowledgement of this issue from 1P team. Thank you!