I just got the email notification that we can test passkeys with the newest beta browser plugin. I couldn't resist and test this immediately.

I created an additional passkeys for my Google account to be stored in 1Password. Saving this to 1Password worked, and logging in with this also seemed to work. It's not easy to detect if I used the built in passkeys support or the 1Password passkeys support, but I'm reasonably sure I actually logged in with 1Password's passkey.

The same with my private Microsoft account: Created an additional passkey for it and saving it in 1Password. Logging in with it also worked fine.

Then I went to my Android smartphone and tried logging in to the Microsoft account in chrome - anything except push notification and password isn't offered, so I assume passkeys is only supported for the desktop currently.

Then I went to a Windows 11 desktop (it's a vm, accessed it with rdp, so without Windows Hello!) where I never used passkeys before. I tried logging in to the Microsoft account with Chrome. Lo and behold, it pulled the cloud-synced passkey from 1Password! This worked!

Then I tried to login to my Google account on that machine. This wasn't successful. Google asked for my password and didn't offer any other option except sending the usual push notification to the smartphone.
\nAfter I successfully logged in with that, Google offered activating passkeys. I started the workflow, however it wanted to create a new Passkey and the 1Password browser plugin offered saving this to 1Password. Since I already had a passkey for this account in 1Password, I stopped and didn't save another one - I guess it's supposed to have only 1 passkey for the same service in 1Password (in this case: my Google account).

So this was half successful: unable to pull an existing passkeys from 1Password for use with Google, but successful in recognizing the passkeys generating and storing workflow. Might have to do with the rdp connection and missing Windows Hello. Unfortunately, I don't currently have a second physical desktop machine to test a cloud-synced passkey on a local machine without rdp.

1Password Version: 8.10.7
\nExtension Version: 2.12.4
\nOS Version: Windows 11
\nBrowser:_ Chrome

I just got the email notification that we can test passkeys with the newest beta browser plugin. I couldn't resist and test this immediately.

I created an additional passkeys for my Google account to be stored in 1Password. Saving this to 1Password worked, and logging in with this also seemed to work. It's not easy to detect if I used the built in passkeys support or the 1Password passkeys support, but I'm reasonably sure I actually logged in with 1Password's passkey.

The same with my private Microsoft account: Created an additional passkey for it and saving it in 1Password. Logging in with it also worked fine.

Then I went to my Android smartphone and tried logging in to the Microsoft account in chrome - anything except push notification and password isn't offered, so I assume passkeys is only supported for the desktop currently.

Then I went to a Windows 11 desktop (it's a vm, accessed it with rdp, so without Windows Hello!) where I never used passkeys before. I tried logging in to the Microsoft account with Chrome. Lo and behold, it pulled the cloud-synced passkey from 1Password! This worked!

Then I tried to login to my Google account on that machine. This wasn't successful. Google asked for my password and didn't offer any other option except sending the usual push notification to the smartphone.
\nAfter I successfully logged in with that, Google offered activating passkeys. I started the workflow, however it wanted to create a new Passkey and the 1Password browser plugin offered saving this to 1Password. Since I already had a passkey for this account in 1Password, I stopped and didn't save another one - I guess it's supposed to have only 1 passkey for the same service in 1Password (in this case: my Google account).

So this was half successful: unable to pull an existing passkeys from 1Password for use with Google, but successful in recognizing the passkeys generating and storing workflow. Might have to do with the rdp connection and missing Windows Hello. Unfortunately, I don't currently have a second physical desktop machine to test a cloud-synced passkey on a local machine without rdp.

1Password Version: 8.10.7
\nExtension Version: 2.12.4
\nOS Version: Windows 11
\nBrowser:_ Chrome

benmattison Do you have the beta extension up to date (version 2.12.0) in the other browsers you use ?

Note : it did not went automatically on one of my browser (it should have after some time...). To force, just uninstall and then reinstall the extension (from the Chrome Store which is usually faster at delivering the updates).

I am also confused about the passkey functionality. I have installed the beta extension in Firefox and Chrome on a couple of computers, and I'm able to save a passkey and then use it to log in in the same browser on the same computer. When I look in the other browsers, I can see that the passkey is being synced through 1Password. But if I try to log in, it asks for passwords. What am I missing?

I've been able to create a passkey (Google account) but so far I've been unable to actually use a passkey to log in. On multiple sites, Chrome will pop up a window saying \"Use your passkey\" and \"Choose which device has the passkey for [site]\" and it lists:
\n* Windows Hello or external security key
\n* Pixel 7
\n* Use a different phone or tablet

It appears that since I have other passkey devices available Chrome is not allowing 1Password to handle it?

Windows 10, 10.0.19043 Build 19043
\nChrome: Version 114.0.5735.110 (Official Build) (64-bit)
\n1Password in the browser 2.12.0, 21200003, on BETA channel

On my side for Adobe : creation seems to work BUT
\nto login (InPrivate via same or another browser): it sends out a verification code to my email, then offers to login via :
\n- Password
\n- Passkey

When choosing Passkey it fails with an error message (something went wrong).

Except the fact it does not actually work with Adobe, asking a password or a passkey at that step (with the requirement of a verification code) do not add to the user experience at all.
\nFor now, I'll stay with the good old password option with them.

\n

By the way, @1password: if you're in the Fido alliance and have a say around passkeys, it might be a good idea to encourage passkey providers to use a unified terminology for passkeys.

\n

I agree 100%

Creating a passkey for adobe.com worked. However, many redundant/duplicate URLs were added as website url during the process.

By the way, @1password: if you're in the Fido alliance and have a say around passkeys, it might be a good idea to encourage passkey providers to use a unified terminology for passkeys.

In English, it's mostly \"Passkey\" or \"Passkeys\", but also \"passwordless\". Or still \"Security Token\". In other languages, it's a mess. Almost not possible to determine that passkeys are meant. Everyone makes his own different translation. Adobe calls it in German \"Hauptschlüssel\" (if translated back to English, would be \"Master Key\" or \"Skeleton Key\").

Passkeys is a new technical term and name not to be translated. Please establish it as such.

I have the identical problem as @oxalate. Went through the same process twice to be sure and got two 1password passkeys showing in the account, although only one seems to be stored in 1password, but never had the 1password passkey sign-in prompt. Tried installing windows 11 1password beta program in case it was related to having beta and non-beta code on the same machine.

1Password Version: 8.10.7 81007036 on BETA channel
\nExtension Version: 2.12.0 2120003 on BETA channel
\nOS Version: Windows 11 Pro Build 22621
\nBrowser:_ Chrome 114.0.5735.110

I tried the same with a Google account. I am currently testing with one instance of Google Chrome on a Mac, on an Incognito session. I successfully added a Passkey and have been able to use it to log in again after logging out.

But if I close Chrome and reopen a new Incognito session, Google only prompts me to use the password and not the passkey anymore. Does anyone know why Google might be having this peculiar behaviour?

I got my google account set up with a Passkey, but it still has the password. Am I going to be able to remove the password?

I'm having the same issues using 1Password-saved passkeys to get into Google accounts. This happens on both a Windows 10 machine with Windows Hello! enabled and on a MacBook Pro with Touch ID.

1Password saves a passkey when I set one up in the Google account, but if I log out and try to log back in with a passkey, Google only offers me the opportunity to log in with my Android phone's auto-generated passkey, and not with the 1Password-saved passkey. If I pick \"use another device\", Windows Hello! prompts me to insert a physical security key (which I don't have) instead of using my actual Hello! authentication method.

I could sign in to my Google accounts using machine-specific passkeys created prior to the release of the 1Password beta, so the issue isn't entirely on Google's side. It seems as though the beta isn't correctly presenting my newly-saved 1Password passkey in a form that Google recognizes as a login option.