Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Former Member
3 years ago"signing failed for" after multiple denies [CLI] [SSH Key] [SSH Agent] [Terminal]
Well, first of all I need say that I have a lot of SSH Keys because I'm work on multiple projects on the same time using git. So, a lot of them force-me to use SSH Key to make a pull or push of code....
floris_1P
1Password Team
3 years agoIt's not likely we'll be making our prompt rate limiter more lenient at this time, so if you need separate SSH keys per repo, a Gitconfig / shell script / SSH config kind of workflow would likely be more promising at this point.
For example, you could look into adding a small git
shim that sets GIT_SSH_COMMAND
based on the directory or Git repo name, e.g. using git config --get remote.origin.url
or git rev-parse --show-toplevel
. And then in that script use the repo name to point to a certain .pub
file on disk: GIT_SSH_COMMAND="ssh -i ~/.ssh/$REPO_NAME.pub" /opt/homebrew/bin/git "$@"
You do have to download all the public keys from 1Password to disk once. (There are ways to also automate that part if you want, but we won't promise a stable API there)
Let me know if that helps.