391
I don't like passkeys | Ethan Hawksley (hawksley.dev)
submitted 1 month ago by to c/technology@lemmy.world
150 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 month ago (4 children)

android doesn't allow 3rd party apps to use passkeys nor autofill 2fa consistently. For passkeys, you are forced to use google services for it, or loose access, making it pointless. TOTP codes meanwhile can at least be copied and pasted manually from a password manager.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 1 month ago* (3 children)

    https://developer.android.com/identity/passkeys/manage-passkeys

    Actually not, 3rd party Android apps can act as passkeys providers

    With Bitwarden you can even do your own self hosted sync of passkeys

    https://bitwarden.com/blog/bitwarden-passkeys-mobile/

    Any app where it doesn't work has chosen to not use the right API

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 month ago (2 children)

    It's android version dependent. Only 14 and up support 3rd party providers.

    Passkeys are supported on devices that run Android 9 (API level 28) or higher.

    On many devices, Credential Manager stores passkeys to Google Password Manager by default. Users can choose other password managers as its passkey providers in the System Settings on Android 14 or higher.

    Given the slowness of android version rollouts, this will be an issue for a long time.

    I also think supporting older androids is pushing apps to do it the "wrong" way and making it google specific.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •