Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
SSH keys issue in latest version
1Password updated yesterday to the latest (current) version - 1Password for Mac 8.12.0 (81200013) - and since then using SSH keys has broken where I have different accounts for the same service. I'm on MacOS Tahoe (26.2).
In my particular case I have different keys for different Azure DevOps environments. But when I perform a git action 1Password goes through the process of getting me to authenticate with the different providers, but it hits the first DevOps instance, authenticates, and then doesn't move on to the next one. Normally it goes to my most frequently used one first, but that's not happening any more, so I have to cancel my way through until I get to the one before and start approving again. It's a bit hard to explain so, here's the general flows when I'm trying to connect to DevOps for company 1.
Flow 1 Approvals - Fails
Github - Approve
Codeberg - Approve
DevOps (comp 2) - Approve
Flow 2 Approvals - Fails
Github - Deny
Codeberg - Deny
DevOps (comp 2) - Deny
Local Forgejo - Deny
<stops>
Flow 3 Approvals - Works
Github - Deny
Codeberg - Deny
DevOps (comp 2) - Deny
Local Forgejo - Approve
DevOps (comp 1) - Approve
In flow 2, I've no idea why it doesn't move on to the second DevOps key if I don't approve the key before it.
I solved my problem by removing the Personal vault from my https://developer.1password.com/docs/ssh/agent/config/
8 Replies
I'm having the same problem and the solution doesn't solve the problem. I never had an ssh agent config and 1Password was able to cycle through the ssh keys as it's supposed to even when I had multiple ssh keys for the same service. Now it fails at the first authentication failure.
Please tell us which version we can revert back to to get the correct behaviour.
I am also experiencing this issue. I now have to cycle through my keys and keep hitting "Deny" until I get to the working key. I have never had to do this in the past.
Same exact problem here. Just started this week on MacOS and I'm seeing SSH keys offered out of order with what's specified in the agent config.
I'm having what I think is the same problem with GitHub. I have a personal ssh key and a work ssh key. My work one is authorized with SSO, but I keep getting intermittent errors saying my key is not authorized. I think the wrong key is being used and not moving on to the next one that is authorized.
I solved my problem by removing the Personal vault from my https://developer.1password.com/docs/ssh/agent/config/
Thanks. I didn't have the agent config file, so I ended up creating one and adding all my SSH keys individually so they're checked in a better order. So it's not fixed the issue, but I can at least work around it for now
