Multiple selected SSH Keys don't work with same server

[broadbeanprop]

Authentication fails when multiple SSH keys are selected and the required key is not at the top of the list.
When the required key for the repository is listed first, it works fine, but that obviously beats the purpose of having multiple keys selected.
I'm currently on version 1.57.1.0.

[DanPristupov]

Can you confirm this with a new pair of keys?

I just tried many combinations and each of them worked properly for me. I tested with GitHub.

[broadbeanprop]

I removed all keys and generated new ones through the Fork UI, problem remains the same.
I'm using 4 different SSH keys for 4 different Azure DevOps environments, 3 of them are totally different accounts/email addresses, so 2 environments share the same email address.

For testing purposes I added an SSH key to my GitHub account on the bottom of the list, and that works fine, so this problem seems to be related to Azure DevOps.

Update:
I also tested having the GitHub key first and then a single Azure DevOps key second, and authentication fails on the DevOps connection, so it should be easy to reproduce.

[DanPristupov]

Looks like the problem is that Azure DevOps doesn't handle multiple ssh keys properly.

[broadbeanprop]

Looks like the problem is that Azure DevOps doesn't handle multiple ssh keys properly.

Ah, nothing you can do about it then I assume?

The ability to select an SSH key for a workspace would be a nice workaround in my case. Together with #1073 would make workspaces an awesome feature.

[paulogodinhoaq]

I am seeing the same issue with GitHub private repositories, I need to manually unselect all other keys in order to interact with it.

[jeastburn]

I was having the same issue using SSH keys with Fork across Azure DevOps, GitLab, and GitHub. I got everything working by leaving all keys unchecked in the Fork SSH Key configuration dialog and updating my ~/.ssh/config file so it used the correct key based on the host. https://teilin.net/configuring-multiple-ssh-keys-with-azure-devops/

[winternet-studio]

I was having the same issue using SSH keys with Fork across Azure DevOps, GitLab, and GitHub. I got everything working by leaving all keys unchecked in the Fork SSH Key configuration dialog and updating my ~/.ssh/config file so it used the correct key based on the host. https://teilin.net/configuring-multiple-ssh-keys-with-azure-devops/

Oh, this was a Godsent comment! @DanPristupov , could a note about this be added in the Configure SSH Keys dialog? I know it changes to say "default system ssh-agent" when nothing is checked but I didn't even notice that, and its effect - allowing for use of multiple keys - is not apparent to the user (described further in #1642 (comment)). Then you can also disgard the feedback I sent you on this issue a couple of days ago ;)

[ltumasov-hc]

I have two GitHub SSH keys — one personal, one work.
If I use only one key, everything works.
If I use both keys, the second key doesn’t work.
I can make it work using ~/.ssh/config and repository aliases, but it’s not convenient.

Expected:
I want to just add both keys in Fork UI and have them work automatically for the right repo. May be you can add filed like this key for this repo.

Actual:
Fork only uses one key correctly. The other one fails.
Notes:
Works fine in Git Bash if I use config/aliases.