Repository navigation
Cred.sshKeyNew not working: Too many redirects or authentication replays #511
Description
Hello everyone,
I am trying to automate pushing to a GitHub repository using NodeGit.Cred.sshKeyNew, but it looks like I am not able to get this working somehow. NodeGit.Cred.userpassPlaintextNew works just fine.
This is what I have:
}).then(function(remoteResult) {
remote = remoteResult;
remote.setCallbacks({
credentials: function(url, userName) {
return nodegit.Cred.sshKeyNew(
userName,
path.join(__dirname, "..", "..", "data", "mykey-rsa.pub"),
path.join(__dirname, "..", "..", "data", "mykey-rsa"),
"myPass"
);
}
});
return remote.connect(nodegit.Enums.DIRECTION.PUSH);
})Which always results in: Error: Too many redirects or authentication replays.
I did double check that:
- paths to the public and private key files are correct
- the key is properly installed on GitHub
- the key has been generated with
ssh-keygen -t rsa - the key's password is correct
Am I doing something wrong there?
Activity
tbranyen commentedon Mar 24, 2015
Have you looked at https://github.com/nodegit/nodegit/blob/master/test/tests/clone.js#L92-L114 by any chance?
dcodeIO commentedon Mar 24, 2015
Yes, looked over the test cases as well. If you intended to hint me at something, I'd be grateful for an explanation.
tbranyen commentedon Mar 24, 2015
@dcodeIO the only hint there is that it's a working example, unfortunately with the code you provided I don't know what the bug is. Maybe try asking in the #libgit2 channel on IRC?
mikalai-s commentedon Apr 14, 2015
I used to have the same issue... In my case remote URL was set to
httpsinstead ofssh.johnhaley81 commentedon Apr 14, 2015
@dcodeIO I think that @mikalai-silivonik is correct. If you're using
NodeGit.Cred.userpassPlaintextNewand that's working then you're not using SSH and no SSH key in the world is going to authenticate you into an HTTPS session. Try switching protocols.dcodeIO commentedon Apr 14, 2015
Stupid me. Thanks!