TouchID UX: compared to 1Password (particularly for SSH operations)

[colemickens]

Hi,

(I think/hope this one is self-evidently not dependent on the server implementation, but I will say that I’m using Vaultwarden.)

The Bitwarden client is quite good, but on macOS, there are a specific interaction that cause a bit more friction than the similar scenario with 1Password. I notice these a lot because I use Bitwarden for my personal stuff, and my job uses 1Password.

1. Bitwarden requires multiple contacts to authorize SSH key usage with TouchID.
   1. The app shifts me to a workspace if the Bitwarden window is open.
   2. The app requires me to start the TouchID process.
   3. (TouchID happens)
   4. The app requires me to then authorize the SSH key usage.
2. Sometimes, a focus shift happens, or Bitwarden changes workspace, or maybe it’s that it doesn’t switch when it’s already unlocked. But basically, a small percentage of the time, this happens, and a small percentage of the time I forget to check for it. This results in me staring at my terminal wondering why Git is hanging. Eventually I switch workspaces back and authorize the key use.

1Password, on the other hand:

• immediately triggers TouchID, specifically prompting that it will use my key, it’s one tap and done

I’m wondering if this is because of cross-platform common denominator (which makes sense). Either way, it would be nice if this could be streamlined. Maybe it’s an intentionality thing, and if so, then maybe this could be optional?

Thanks, I hope this can be considered/voted on.