Removing a key form remote ssh on mac how to#

I seemed to spend a crazy amount of time trying to work out how to change access to a Git repository (repo) from HTTPS to SSH to avoid password prompts when pushing changes to BitBucket and GitHub.

Add the private SSH key to your keychain.

Add the public SSH key to your remote Git server.

Xcode git ssh authentication failed, works OK from command lineĪ minor contribution, but it's a start. Xcode 12 authentication failed because the credentials were rejected

Xcode 12 authentication failed because the credentials were missing Xcode git ssh authentication failed because the credentials were rejected URLĪfter completing those steps, I was able to open the original project which was causing grief in Xcode, and could successfully pull, fetch, whatever.įor the benefit of future Google searches: Start Xcode and attempt to clone a project into a temporary directory using your ssh://. 'cd /tmp git clone Terminal.)Ĭode Block $ defaults delete .xcode IDESourceControlKnownSSHHostsDefaultsKey I thought I might contribute by combining them: The steps here allowed me to resolve the problem, but the steps were scattered about a bit. It would complain about its inability to authenticate using the ssh key. I could 'git clone', 'git fetch', 'git pull', whatever from the command line using ssh keys while talking to a local server machine just fine, but was unable to get Xcode (12.4 running on macOS 11.2.3) to cooperate. I would like to express my appreciation for the comments here, as it resolved the problem I was having. This was tested with Xcode Version 12.3 (12C33) under MacOS 11.1. Xcode's use of ssh appears to just ignore the 'User' directive in. The occasional duplicate entries in the prefs file under DVTSourceControlAccountDefaultsKey appear to be minor issues that can be ignored. There's some (tbd) account/identity daemon/state file that Xcode is chatting with that's caching the old bogus info. Logout and logging in again is not enough. Quit and relaunch of Xcode is not enough. To repeat, after deleting or editing the prefs file you need to reboot. (or use a plist editor that can process binary files)Įdit .Xcode and find the key 'IDESourceControlKnownSSHHostsDefaultsKey'ĭelete both the key and its data. If you really really don't want to just delete your prefs file, you can do surgery on it to fix it, but it's pretty silly: And then next time it'll even fetch your passphrase from your keychain and you won't need to type it again. Give it the passphrase and the clone will work. Now when you try and clone it with Xcode you'll get the username/password dialog with 'SSH Keys' selected and a request to unlock the passphrase. You MUST REBOOT your computer at this point. 'cd /tmp git clone Xcode's preferences file in ~/Library/Preferences/.Xcode add your public key to the remote user's. If still needed, fix your ssh problem (e.g. The basic idea is that if Xcode's use of ssh fails you will get a bogus error message from Xcode about not matching previous requests and it is stuck. There are many other (far shorter) ways to get stuck with this failure, but this demonstrates that there is no 'previous request' or previous saved-state involved. ssh/authorized_keys file, Xcode is still stuck with the same error message. Additional attempts to clone just gets the same error message without the username/password dialog prompts.Īnd even after fixing ssh by adding your public key to the remote user's. ssh/authorized_keys file, but this is the message you get from Xcode.Īnd now it's stuck. The real error is that your newly created public key is missing from the remote. Now you get 'An unknown error occurred' and 'username does not match previous request (-1)' Now it (appropriately) fails and you see 'Unknown error' in the dialog. Hit Clone, then Trust to accept the remote hosts's id. Hitting 'SSH Keys' again will get it to notice they exist now. Minor bug: the dialog still thinks there are no existing keys. Give it a passphrase, let it save your keys in the default.

Xcode notices you don't have ssh keys yet, and offers to create them. In the username authentication dialog that pops up, switch from 'Username and Password' to 'SSH Keys' both SSH and non-default remote username. ', paste the URL into the 'Enter repository URL' field at the top. ssh directory or your public & private keys yet To trigger the bug (this is reliable, but is not the shortest method):Ĭreate a new local user (to be sure of no previous state)ĭo not create the. I've been able to both trigger and repair this problem.

Removing a key form remote ssh on mac