BUG: 1Password SSH agent not working

[farski]

Describe the bug I've recently started using the SSH Agent that 1Password introduced in version 8. When selecting SSH Agent as the option for SSH Authentication with an SSH Tunnel, I receive the error All configured authentication methods failed. When using a file of the same key found in the SSH agent, the connection works as expected.

Version Information (please complete the following information):

• OS: macOS
• App Version 3.6.2

[elsbrock]

This may be the reason: https://developer.1password.com/docs/ssh/agent/advanced#ssh-server-six-key-limit

[farski]

I don't believe that's the issue for me, since these keys work via 1Paassword when connecting to the same DBs with clients other than Beekeeper.

[elsbrock]

Beekeeper may not be aware of the SSH agent. Can you check this? https://developer.1password.com/docs/ssh/agent/compatibility#configure-ssh_auth_sock-globally-for-every-client

[farski]

I'm having some trouble with the launch config, but opening Beekeeper from the command line with open -a after exporting SSH_AUTH_SOCK does seem to be working. Need to dig into it some more when I have time.

[belaarany]

I have the same issue on Windows 11. I checked the links mentioned above but there are no solution for Windows. Anyone may have a workaround for Windows?

[farski]

Closing the loop: both methods suggested in the docs (open -a and creating the launch agent) do work.

I think ideally it would be great if Beekeeper natively supported IdentityAgent in ~/.ssh/config so that they weren't necessary, but that is probably better classified as a feature request than a bug.

[joeld-win]

Reopening the loop, there are no methods that work on Windows.

[DKhalil]

Might be related to #1444