Passkeys in Chrome - 1P not being triggered

Hey cryptochrome,

I understand the trouble of starting over your 7 Google accounts. Do you mind testing with one of the accounts and see if the newly created passkey would work there?

Meanwhile, do you have all of your Google accounts as the Workspace type?

Hi kevin_li - I have 7 Google accounts (I know, I know). They all have passkeys, all created on June 9th (I think that's when Google made passkeys available to Workspace customer). I would really want to avoid having to delete and recreate them all.

What's the culprit, you think?

Just want to stress again that these very same passkeys work absolutely fine in Chrome on macOS.

Hey cryptochrome,

Can you confirm the date of the passkey created in 1Password? If it was created before Aug 9th 2023, let's delete the passkey in 1Password and your Google account. Then, let's re-create one to test.

Let us know how it goes.

--Kevin

Yes steph_giles, I can see it there.

Hey cryptochrome,

Thanks for getting back to me.

If you click on the 1Password icon in your browser toolbar can you see the passkey saved within your Google login item?

Hi steph_giles,

this happens on Chrome 117.0.5938.150 (Official Build) (64-bit), but it also happened in previous versions of the browser.

The 1P extension is currently at version 2.15.1 - 21500107, on STABLE channel. But I had this issue with previous versions as well.

Here is a screenshot of what it looks like when I try to sign in to my Google account, which triggers the passkey workflow:

And here is a screenshot showing my Chrome settings for passwords (as you can see, 1P is integrated here):

Looks like Chrome is completely ignoring 1P when passkeys are requested.

Note that it works perfectly fine on macOS, with the same browser settings (they are actually synced).

Thanks
Sascha

Hey cryptochrome,

Can you let me know which browser you are using and the version of 1Password in your browser you have installed on Windows?

Thank you!