Unable to sign in to a Google account using a saved passkey

Hi everyone,

Thank you for the reports about this issue. We've also validated that passkeys for Google are being saved correctly in 1Password, but that passkey login is sometimes not offered as an option when you go to sign to your Google account using a different device. We're in touch with the team at Google about this, and I'll post any updates here when there's news.

-Mitch

Feels like the issue is on the Google side. I'd expect if I logged in on a device and my account had the passkey option, it would still be an option I could select. But when you try to login to a google account that has no history or cookies on the device, it only shows password only.

Unless Google has some sort of detection method about the browser/device you are on, and decides if it's "passkey" compatible before showing an option.

Hopefully Google can give you some clarity on the matter, cause at the moment, can't use passkeys on Google. Which is fine since it's BETA, but even if you get the option, still seeing the "Windows Hello" asking for physical medium popup.

I actually don't think this is on the "Google side", at least not entirely, and here's why. I'm using Macos Ventura, FWIW.

When I save a passkey to iCloud Keychain, Google recognizes it and lets me use it to log in the next time. It works every time. But when I save a passkey to 1Password instead, Google never gives me the prompt, even if I click "Try another way". I have the latest beta extension installed and beta desktop client. "Skip password when possible" is enabled.

I've tried using a passkey saved in 1Password on 4 different browsers (Chrome, Edge, Safari, & Firefox), both desktop and mobile, with multiple different Gmail accounts, and tried opening the pages multiple different ways.... nothing seems to trigger the passkey prompt. I've tried both free Gmail accounts and Google Workspace accounts (for which I am the administrator) with the same result.

I did a quick scan of the passkey API documentation and when a client visits a server that supports passkeys, the server does a query of the client to find out what authentication methods it supports.

I have two theories about what may be happening
1. 1Password is not responding to this query to let Google know that passkey is an available option, or
2. Macos is intercepting this query and responding to it before 1Password has a chance.

TheKnack. BUT: for me it doesn't work with iCloud Keychain either - no difference...

Hi, I have the same problem where google does not offer Passkey as a sign-in option.

However, if I create a new Passkey and try to login again using the same google account it does show Passkey as a sign-in option.

What is important here is that whatever browser I'm using, clearing cookies will cripple google login page and Passkey no longer shows as an option even though 1Password has the Passkey credentials.

Hi @dwk. Strange. My browsers are set to clear cookies when they close and I'm always offered a passkey sign in after startup. In Windows it uses Window Hello for passkey and on macOS it uses 1Password. I generally use Edge.

Now it works for me on Mac. Not sure if this is cause by change on google side or update on 1Password extension side?

telephoneman2 - It worked for me in Chrome. I don't feel like logging out of everything to try it in Edge (which is my primary browser).

TheKnack

I just tried again on Chrome on Windows 11. Latest version of both. Still not working

Passkeys were working for me on Chrome, but now they aren't after the July 3rd beta update. Before 1Password would at least receive and store the passkey, Google just wouldn't request it on sign-in. Now Edge grabs the passkey and stores it, even though I have Edge password management disabled, and 1Password doesn't detect that I created a passkey.