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...
  • exu@feditown.comOPEnglish
    161·
    20 days ago

    QR codes are good 50% of the time; when you’re trying to log in on a pc.
    The reverse case is extremely annoying

    • unskilled5117@feddit.orgEnglish
      9·
      20 days ago

      Could you elaborate? I am assuming that everbody would have the password manager on their mobile phone with them, which is used to scan the qr code. I think that’s a reasonable assumption.

      I agree that if you wanted the pc to act as the authenticator (device that has the passkey) it wouldn’t work with qr codes. But is that a usecase that happens at all for average people? Does anyone login to a mobile device that you don’t own, and you only have your pc nearby and not your own mobile phone?

      • exu@feditown.comOPEnglish
        71·
        20 days ago

        I’m thinking of phone recovery, where you’re trying to get all your stuff back on a new device.
        With a password manager, simply logging in will get you there and until passkeys can be synced automatically just like passwords this will need to be handled somehow.

        • unskilled5117@feddit.orgEnglish
          12·
          20 days ago

          I hope I am not misunderstanding you. What you are worried about is passkeys in the password manager not syncing to new devices? They are though, with password managers that support passkeys like Bitwarden, ProtonPass, 1Password etc…

          Currently using it on Bitwarden, if I log in to a new device, the passkeys are there.

          • exu@feditown.comOPEnglish
            3·
            20 days ago

            You understood correctly. Seems like I missed some news on the syncing front.