1Password on Mastodon

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

Community Member

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 is ran from/by a Node.js script when using a key in a repo that uses SAML single sign-on

The problem

Considering the following SSH config:

Host *
  IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock"

Host github.com
  IdentityFile ~/.ssh/keys/github.pub

Where github.pub is the public key of an SSH key from my vault.

Using the git CLI in a regular context (fish shell 3.5.1 in iTerm2 3.5.0beta9) works fine and prompts the Agent like expected:

However, running inside the same repo but using the git command inside a script causes an error. Considering the following script:

import { exec } from "child_process";

(async () => {
    'GIT_SSH_COMMAND="ssh -v" git pull',
    { cwd: process.cwd() },

yields the following error when ran

debug1: SSH2_MSG_EXT_INFO received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/damien/.ssh/keys/github.pub ED25519 SHA256:4qAKLnbwSPfhZggpEDaJRo5SQe982Do8A6vOS6jAcEM explicit agent
debug1: Server accepts key: /Users/damien/.ssh/keys/github.pub ED25519 SHA256:4qAKLnbwSPfhZggpEDaJRo5SQe982Do8A6vOS6jAcEM explicit agent
sign_and_send_pubkey: signing failed for ED25519 "/Users/damien/.ssh/keys/github.pub" from agent: agent refused operation
debug1: No more authentication methods to try.
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

With those interesting warnings in 1Password's log file when the script runs

WARN  2023-01-06T20:16:59.064 tokio-runtime-worker(ThreadId(6)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
WARN  2023-01-06T20:16:59.064 tokio-runtime-worker(ThreadId(6)) [1P:ssh/op-ssh-agent/src/lib.rs:426] Unable to get client_info for pid: 1077

My current (hacky) workaround

After battling for two days with my SSH config file I figured out a workaround. It's not pretty but it works fine:

  • Remove the Git bit from my main ssh config
  • Create another config file in .ssh, named config-git
  • Put the Git bit from before in that newly created file
  • Set the GIT_SSH_COMMAND value to ssh -F ~/.ssh/config-git
  • Export the private key of my Git SSH key
  • Run ssh-add --apple-use-keychain <path_to_key_file>
  • Now both a regular git pull and the script above works.

1Password Version: 1Password for Mac 8.9.12 (80912004)
Extension Version: Not Provided
OS Version: macOS 13.1
Browser:_ Not Provided


  • EramdamEramdam
    Community Member

    It seems i can't edit my message but, after testing some more, the default configuration (one single file and the 1P agent globally) sometimes work and sometimes doesn't. It might work on one run of the script above but then won't on another one. It's all very weird.

  • sitepodmattsitepodmatt
    Community Member
    edited January 11

    Is this your full script or a minimal reproduction - is the environment via process.env passed along the full chain so things like DBUS_SESSION_BUS_ADDRESS env var available? You can obviously test this easy enough , try to diff the env output for times it works and times it doesnt

        { cwd: process.cwd() },

    btw, its kind of a guess that its DBUS_SESSION_BUS_ADDRESS based on

  • EramdamEramdam
    Community Member
    edited January 12

    The script in my OP is a minimal reproduction. The full script is a deploy script we use at work, so I can't really share it.

    And AFAICT the difference in the env content doesn't seem really useful


  • EramdamEramdam
    Community Member

    Now that I post and updated to the newest Nightly build (81000010), I feel like it's all working as expected with the default config. I'll report back to see if the issue comes back πŸ˜…

  • jody.h_1Pjody.h_1P

    Team Member

    Hey @Eramdam, thanks for the updates, and apologies for not getting back to you sooner. I'm happy that it seems like things are working for you now, but if you run into troubles feel free to report back and we'll take a look.

  • EramdamEramdam
    Community Member
    edited January 19

    Okay so: regular git operations within the affected repos work fine with the default configuration but running git inside the provided simple Node script still fails randomly.

    The deploy script we use at work basically does this

    import {exec} from 'child_process';
    (async () => {
      exec('git rev-parse ....', {cwd: process.cwd()}, () => {
        exec('git fetch ...', {cwd: process.cwd()}, () => {
          exec('git log ...', {cwd: process.cwd()}, () => {
            exec('git push origin foo:bar', {cwd: process.cwd()}, console.log);

    So I'll run into situations where the git fetch succeeds but not the final git push, or vice versa or sometimes everything will work or sometimes nothing will. I'm starting to think that when it works it's "by accident" because I can't figure out a clear pattern 😞

    This is all while running 1Password for Mac 8.10.0 (81000012)

  • sitepodmattsitepodmatt
    Community Member
    edited January 20

    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

    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

  • PeterG_1PPeterG_1P

    Team Member

    HI @sitepodmatt, I'm sorry to learn that the SSH agent hasn't met your needs. There are some improvements coming which we hope will improve your experience substantially. Stay tuned for updates ahead - we'll be happy to have your feedback.

  • EramdamEramdam
    Community Member

    I switched back to using my original workaround for now. It requires adding my private GitHub key to my OSX ssh-agent but it works πŸ˜…

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file