Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Add support for SSH IdentityAgent #645

Closed
CrazyVito11 opened this issue Oct 15, 2023 · 1 comment
Closed

[Feature] Add support for SSH IdentityAgent #645

CrazyVito11 opened this issue Oct 15, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@CrazyVito11
Copy link

CrazyVito11 commented Oct 15, 2023

Issue
I use 1Password as my identity agent in order to authenticate SSH requests, but GittyUp doesn't seem to support this if I add it to the ssh config.

image

I've added the IdentityAgent to my SSH config file and works properly if I execute GIT commands via the terminal, but not via GittyUp. Maybe it doesn't load the config properly?

Host *
        IdentityAgent ~/.1password/agent.sock

Workaround
I currently use a workaround by viewing and creating commits using the UI, but fetching/pulling and pushing via the terminal.

Requested functionality
That support for IdentityAgents is added or that the possible bug in the SSH config support is fixed.

Please let me know if you need any more information!

@Murmele Murmele added the enhancement New feature or request label Oct 27, 2023
@CrazyVito11
Copy link
Author

It seems like it suddenly started to work, so it was probably a misconfiguration of the 1Password SSH agent on my end. 😅

I did make a change to my system yesterday for Tabby, as that also didn't seem to recognize the 1Password agent.
After then consulting the 1Password documentation, I found that applying the SSH_AUTH_SOCK globally fixed the issue for Tabby, and that is also probably why GittyUp suddenly started to work.

The command I ran can be found here: https://developer.1password.com/docs/ssh/agent/compatibility#configure-ssh_auth_sock-globally-for-every-client-1

I will close this issue now, and hope that this information might also help someone else in the future. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants