Forum Discussion

Former Member's avatar
Former Member
2 years ago

Passkey blocking login with other physical key

Many websites experience this type of problem where the 1p blocks other U2F/FIDO 2 devices.

If 1p is locked the Chrome throw the following errors and stop the browser to process the other tokens. (Both Register and Authenticate)
Error: Error response received for message webauthn.js:4:51116

If 1p is unlocked, we could use other token to do the Register by close the 1p popup windows.

However, we could not use other token to do the Authenticate if that website already has 1p passkey registered. The 1p passkey will automatic Authenticate if the allowCredentials has the pubkey of passkey.

Example site
https://webauthn.io/

1Password Version: Not Provided
Extension Version: 1Password in the browser 2.12.0 21200003, on BETA channel
OS Version: 12.6.6
Browser:_ Chrome Version 114.0.5735.90 (Official Build) (x86_64) / Firefox 113.0.2 (64-bit)

browser extension
  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    2 years ago

    @VEKXX0H2N7

    I'm sorry for the late reply. Are you still unable to use your hardware security key when using the latest version of 1Password in the browser: 1Password Releases

    @Algorithm5053

    Can you tell me a little more about the issue that you're running into? Are you able to use a security key in your browser? What error message do you see? Which browser are you using?

    I look forward to hearing from you.

    -Dave

  • Former Member's avatar
    Former Member
    2 years ago

    When 1p lock/unlock, the 1p browser extension blocked other U2F devices.

    async function get(options) {
    const response = await navigator.credentials.get(options);
    response.toJSON = ()=>getResponseToJSON(response);
    return response;
    }

    webauthn-json.browser-ponyfill.js:204 Uncaught (in promise) TypeError: Cannot set properties of null (setting 'toJSON')
    at w (webauthn-json.browser-ponyfill.js:204:18)
    at async rp (webauthn-create.ts:337:30)
    at async rd (webauthn-create.ts:287:5)

    Did the 1p QA/QC people do their jobs? Why, the 1p can ship the broken extension twice??

    Old Thread.
    https://1password.community/discussion/140685/passkey-blocking-login-with-other-physical-key#latest

    1Password Version: Not Provided
    Extension Version: 2.14.2
    OS Version: Not Provided
    Browser: Not Provided

  • Former Member's avatar
    Former Member
    2 years ago

    Hey @VEKXX0H2N7 @Ryan Parman thanks for bringing this up. We were able to confirm the behavior and have reported it to our developers. Hopefully, they can investigate and come up with a fix for this. We're looking forward to updates and lots of improvement down the line.

    ref: dev/core/core#22265