We had originally planned to go all-in on passkeys for ONCE/Campfire, and we built the early authentication system entirely around that. It was not a simple setup! Handling passkeys properly is surprisingly complicated on the backend, but we got it done. Unfortunately, the user experience kinda sucked, so we ended up ripping it all out...
  • @4am@lemm.eeEnglish
    16•1 month ago

    Bitwarden just announced a consortium with Apple, Google, 1Password, etc to create a secure import/export format for credentials; spurred by the need for passkeys to be portable between password managers (but also works for passwords/other credential types)

    • @WanderingVentra@lemm.eeEnglish
      8•1 month ago

      I’m definitely holding off on passkeys until that project is finished. I also don’t want vendor lock in and while that seems like the solution, it seems like they just started working on it.

      • Encrypt-KeeperEnglish
        1•1 month ago

        The interoperability already exists in the protocol webauthn, part of FIDO2 which has been around for almost a decade. Interoperability is not remotely an issue with passkeys. Imported/export is/was and also already has a solution in the works.

        • @morrowind@lemmy.mlEnglish
          2•1 month ago

          So I can use the same passkey from say, bitwarden and windows hello? Why do you even need import export then?

          • Encrypt-KeeperEnglish
            2•1 month ago

            Yes you can use a passkey set up on any given service to authenticate to a service that supports passkeys. You’d need import/export to move a given passkey from bitwarden to Windows.