Forum Discussion

Former Member's avatar
Former Member
3 years ago

Agent doesn't work with Git inside a Node.js script using a SSH + SSO key on GitHub

I've been trying to switch to using the 1P SSH Agent full-time and while it's working great for my regular servers' SSH and commit signing, the SSH Git(Hub) connections are giving me issues when git...
SSH
Former Member's avatar
Former Member
3 years ago

Suggestion. 1password ssh-agent is a buggy disaster, possibly on-par with 1pw v8 ios faceid ongoing saga..

create an ssh-agent per invocation, read in the required key, launch node (the env is ready here with SSH_AUTH_SOCK) and key added, run your script, kill the temporal ssh-agent, job done - no depedency on the terrible 1pw ssh-agent

e.g. a shell script like this call push.sh

```

!/bin/bash

eval ssh-agent
ssh-add <(op read "op://Personal/BitbucketKey/private key")
node myscript.js
kill "$SSH_AGENT_PID"
```

Note op (1pw clumsy CLI) doesn't have a local cache like bitwarden's so expect an extra ~second latency here. No need for any other 1pw crap on your CI/CD box other than CLI tool . Good luck, lmk if any questions

Remove the remote API dependency if you migrate to Bitwarden