Forum Discussion
Unable to sign in to a Google account using a saved passkey
Neither Google nor Microsoft offers me to use passkey as a sign in method.
Am I doing it wrong ?
Thanks
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided
62 Replies
- telephoneman2Super Contributor
@logiclabs that google seems to have issues. There is a dedicated thread for google other people have issues here. That "skip when possible" is enabled, but anyway it not using the Passkey. its using it for 2 factor but not as main login w/o user/password. It's also not working for Safari iCloud Keychain - there it wasn't working since day one when google introduced that feature. For what ever reason it keeps asking for password and user - just for 2nd factor its used for me (where it was asking for OTP before)
- FydonOccasional Contributor
1p_jac I'm using Edge on Windows 11. I have a period in my email address. I have a Windows passkey setup, in addition to 1Password. It prompts for the Windows one first. If I cancel that, there is not an option to use 1Password instead, only my phone or another device (shows QR code to scan). Removing the Windows passkey defaults to using security key as others have mentioned.
When adding the 1Password passkey, 1Password prompted first. Cancelling this allowed me to create the Windows passkey again.
- TataruTaruDedicated Contributor
I'll be honest, I've had issues just changing browsers on the same machine, or using incog/private mode. I even find that without the cookie of a successful login, it just ignores there is a passkey on it.
It's only an issue that seems to apply to Google. No idea what's causing the issue.
- tmuro17New Contributor
A passkey can be created for my Google accounts on my desktop, and though the passkeys are present in 1Password on my laptop, I am not able to use the passkey to sign in. It is unclear to me whether this limitation is on Google's side, or if the 1Password extension is failing to provide some metadata.
1Password Version: 1Password for Mac 8.10.8 (81008012)
Extension Version: 2.12.0
OS Version: Not Provided
Browser:_ Safari, Brave - BackspazeDedicated Contributor
Google has https://security.googleblog.com/2023/05/so-long-passwords-thanks-for-all-phish.html about the release of passkeys for Google accounts, which may shed some light on why it's working the way it does.
- telephoneman2Super Contributor
I played a bit around in google -it seems google is using the passkey as 2nd factor after keying in User/Password. Instead of OTP it grabs the passkey. If you log off google it might keep in a cookie to suppress any 2nd step auth at all after once successful login (especially when you said in login 2nd factor step "don't ask me again") - if you do in private mode or wipe cookies it forces the 2nd factor - I could not find a way to use passkey as main login mechanism. It seems that's just a 2nd factor, but always user/password is mandatory in first step. Similar like you do for 1password.com login - either OTP or passkey
- telephoneman2Super Contributor
1p_jac hello jack, I think this is issue on google side. I just got it rare working - if it worked then just random and only on the same machine. For whatever reason google seems not detect or is willing to detect, that a passkey is waiting for use. Issues appear on windows same like Mac. I tried with iCloud Keychain passkey from Mac safari ->iOS (fail); IOS ->Mac Fail. If it worked then only on same machine - but also here- no pattern found. Now tried same with 1 Password, with additional Safari ->Edge on Mac. Fail (no . in email)
- 1p_jac
1Password Team
Manaburner @logiclabs telephoneman2 oUNderge
Thanks all for letting me know your experience with using passkeys from 1Password in Google so far. Whilst I look further into this on my end, do any of you have a period (.) in your Google email addresses by any chance? I believe this is a newly discovered quirk that the team have on their radar from over the weekend.
Could you also let me know if you're using Mac, Windows, or Linux here since I've only seen this happen in browsers on Windows devices so far.