Chrome extension changed behaviour with 2.4, now showing panel?

hkucharek

Hello!

I can't any longer use the 1password Chrome plugin in development of a webapp that is using WebauthN after login. 1password shows now a panel in the upper right corner of the browser window of the app with "Login with..." (in German) and the title of the webpage.

It breaks the WebauthN process, I get an exception. It only happens in the development environment where the webapp is accessed by a http://localhost:8080/index.html URL. It is (still?) ok with Firefox with the 2.3.8 plugin. Recognized the problem in Chrome with 2.4.0 and it is still there with 2.4.1

---

1Password Version: 7.9.6
Extension Version: 2.4.1
OS Version: macOS 12.6
Browser:_ Chrome 107

sja

I also have this problem.
webauthn.js:formatted:1162 Uncaught (in promise) Error: Error response received for message <create-credential> at webauthn.js:formatted:1162:58 (anonymous) @ webauthn.js:formatted:1162 await in (anonymous) (async) (anonymous) @ webauthn.js:formatted:1671 pn @ webauthn.js:formatted:1647 (anonymous) @ webauthn.js:formatted:2577 postMessage (async) navigator.credentials.navigator.credentials.create @ VM1433:1 (anonymous) @ scripts.js:47 Promise.then (async) registerUser @ scripts.js:37 dispatch @ jquery.min.js:2 v.handle @ jquery.min.js:2

paul.m_1p

Hey @hkucharek and @sja 🙂

I'm truly sorry for any interruption in your development flow caused by this behaviour. We've made some changes on our end and things should be back to normal in the next extension update.

We're hoping to release Passkeys support at some point next year, and hopefully by then we'll have more configuration around deferring to the browser's default handling or turning off 1Password for WebAuthn entirely.

In the meantime - our override is only for port 8080, so if you're able to switch to a different port, that should allow you to keep messing around!

Let me know if that helps!

sja

Nice, thanks for the workaround!

Joy_1P

On behalf of Paul, you are welcome @sja!