I did yet another quick #passkey trial. And again nothing works, problems everywhere I look. Here's Chrome on a Samsung S23. I can tap "Sign in with passkey", then there's a spinning spinner on the button. And that's it.
edit: same behaviour before and after signing up...
=> More informations about this toot | More toots from hambier@mastodon.opencloud.lu
And with my usual browser, Firefox, it's not great either:
=> More informations about this toot | More toots from hambier@mastodon.opencloud.lu
Regarding Google, that one was enabled in the Autofill settings, see screenshot, but if I tap on it it shows a setup screen which asks for my "Chrome password" whatever that is supposed to mean...
So it was "enabled" but dysfunctional...
Does Chrome even use a password that is distinct from my Google password? Anyway I don't really want to get sucked into Chrome.
I'll stick with passwords for another year at least...
=> More informations about this toot | More toots from hambier@mastodon.opencloud.lu
So that "Chrome passphrase" has apparently been set by me. But I never really used Chrome as my main browser. I must have set that passphrase over a decade ago? Anyway, I had to delete all my Chrome data in order to reset it. (understandable)
Now I still can't create passkeys in Google's Password Manager from within Firefox/Android, but it does now work in Chrome. And I can use this passkey in Firefox. Progress. Even though it's one-way. And I can still have Bitwarden set as primary.
=> More informations about this toot | More toots from hambier@mastodon.opencloud.lu
text/gemini
This content has been proxied by September (ba2dc).