Excessive SSH Key Requests

No worries, on re-reading I'm aware my message probably sounded overly negative which wasn't really my intention, I really want this feature to be a success, and it's great to see 1Password investing in it :)

Thank you for letting us know, @rblenkinsopp. We want this to be a seamless process for you!

I just wanted to add to this and say that the feature is great, but as other have said there are an excessive number of dialogs, both overnight and during normal workflows.

The remembering behaviour for authorisation per process is really inconsistent. GitHub Desktop will normally ask for one request and then continue to work without subsequent requests for a while, but at some point, it fails and consistently asks for every request after that.

Likewise, Jetbrain IDEs (Pycharm, Clion etc.) all request SSH auth through a jetbrains-toolbox entity and these requests for a key unlock occur on every request, rather than once for the process. This normally means a git push requires over 2-3 authorisations which is not a great user flow.

In short, I love this feature and the direction of travel, but until the remembering behaviour and mass of dialogues are resolved I'm going to have to stop using it for now as it's rather getting in the way.

This is on Windows 11 and with 1Password Version "1Password for Windows 8.7.0" (80700095, on BETA channel)

Hi folks, thank you for taking the time to describe this issue in detail, and especially to @bendalton for the initial report.

If you're able to share the version of 1Password you're currently using, and the OS you're on, that would greatly help our efforts to investigate as we go forward.

Thank you again - and I'll hope to have more for you on this!

ref: dev/core/core#14789

I just came back from a weekend of not using my work Mac to this problem again. I counted. Before I could interact with 1Password, I had to dismiss 121 of these dialogs!

I second this. For the record, it looks like this may have been introduced in newer versions? GitHub Desktop is the application causing the pain for me (since it seems to poll in the background for updates). Whenever I come back to my computer each morning I have 10+ SSH requests to dismiss.

In earlier versions with the SSH feature, this wouldn't happen and I would only get one request whenever GitHub Desktop next requested my SSH key while I was actively using my computer.

The natural solution to me seems to just replace requests inside a queue as they come in. So if one request comes in and I haven't responded to it by the time the second request comes in, cancel the first request and present the confirmation for only the second request. If the second request is never responded to by the time the third request comes in, replace that one etc etc.

Agreed -- the default behaviour of the command-line ssh utility is less intrusive. Are there any other benefits to using 1P as the ssh server?