Hacker News Reader

Comment by baby_souffle | Hacker News Reader

> So you're saying that if you're inside Apple's walled garden, it works really well! Hmm...

Or google. If you use android and chrome then it all just works.

But god help you if you want to use a password manager to keep everything in sync; I haven't yet found a way for a mobile app or web page to explicitly signal to the device that the passkey to be created should live in $password_manager and not whatever built-in/on-device key-store exists.

So I only really use pass keys for desktop/web things because that's the only place the "store/read from $password_manager" flow _works_.

View on HN

It's probably not something the app or web page should have any visibility or control over. It's more something the browsers and OS should allow a straightforward selection of where you want your passkeys stored (ideally something you can configure the default for globally). But of course the OS and browser vendors are trying to compete to do it, so they're not incentivised to make it obvious or fair.

>I haven't yet found a way for a mobile app or web page to explicitly signal to the device that the passkey to be created should live in $password_manager and not whatever built-in/on-device key-store exists.

On Android 17 (on Pixel) you can select the password service under Settings -> Passwords and passkeys -> Preferred service.

If you have an alternative password manager installed, it will be listed there along with Google's own password manager. iOS has a similar setting but I don't know exactly where off the top of my head.

> On Android 17 (on Pixel) you can select the password service under Settings -> Passwords and passkeys -> Preferred service.

I have this set to my password manager but I still can't _use_ the pass-keys in my password manager to sign in to most apps.

"Most" apps? So it works in some apps, but not others?

Setting your preferred password/passkey manager on Android 17 to 1Password works fine in Chrome and Firefox to log in to any site, presenting passkeys managed in 1Password. It also works in all of Meta's native apps. (I'm pretty sure it works the same in Bitwarden.)

Whatever issue you're having, it's not an inherent limitation of Android passkeys. It might be a bug in your passkey manager…?

> Setting your preferred password/passkey manager on Android 17 to 1Password works fine in Chrome and Firefox to log in to any site, presenting passkeys managed in 1Password

I went to `github.com` in chrome (not my default browser) and firefox and tried to sign in with pass key. I never even got a prompt from 1password to unlock to use the pass key, just a "no pass keys available" message from what looks like the system UI.

When I go to passwords & passkeys, 1password is the only item listed under preferred service. Google shows up under additional services but I have the toggle set to off.

so yeah, I just auto-fill my username and password like it's 2018.

> Setting your preferred password/passkey manager on Android 17

Which approximately no one is using yet. Maybe in two weeks, when the new Samsung flagships roll out, to two months, when they start updating current generation devices...

> to 1Password works fine in Chrome and Firefox to log in to any site, presenting passkeys managed in 1Password.

Perhaps. But does it work with System Web UI, which I imagine is Chrome but have no clue how it's accessed?

https://f-droid.org/packages/de.noisruker.openPasskeyAuth

Use this then totally offline

Works fine on iOS. All my passkeys are in 1Password, and every prompt to use or save a passkey goes through 1P. You can also control which password managers are active on iOS (eg, I disable iCloud passwords, and only allow “autofill from” 1Password.)

So yeah, this is cross platform on iOS, macOS, Windows, and Linux.

Reply on news.ycombinator.com