![sourcetree authentication failed sourcetree authentication failed](https://i.stack.imgur.com/LWVqV.png)
Additionally the GCM also manages credentials using Windows Credentials Manager, or Vault, a secure part of the Windows OS. The use of OAuth means it is now possible to support HTTPS URLs while using a 2FA protected account. The new Git Credential Manager for Windows (GCM), developed by Microsoft, adds support for retrieving and using OAuth tokens for use with Visual Studio Team Services, Team Foundation Server, and GitHub. While this works, SSH is still a little strange in a Windows environment. Which meant switching to SSH for Git and Mercurial URL's. Unfortunately, the use of two-step authentication prevents the use of Basic Auth for authentication. Both Bitbucket and GitHub recommend the use of Two Factor Authentication (2FA) to secure your accounts.
![sourcetree authentication failed sourcetree authentication failed](https://i2.wp.com/nekonoblog.net/wp-content/uploads/2019/04/shutterstock_544549771-1.jpg)
This is true for Git, Mercurial, and REST API calls. More about the authentication changesĬurrently SourceTree only supports Basic Auth credentials for communication with Bitbucket and GitHub services. This will be a great help in providing a more stable experience for users. The new installers also support progressive feature rollouts so we can ship new features to a subset of users, monitor for any regressions, address anything that is found, and then roll the feature out to all users.
Sourcetree authentication failed update#
With this update you'll no longer need Admin rights during installation, so the update process will be much less intrusive.
![sourcetree authentication failed sourcetree authentication failed](https://i.stack.imgur.com/AzgYs.png)
Moving the installed location from %ProgramFiles(x86)%\Atlassian\SourceTree to %localappdata%\SourceTree means SourceTree is installed per user, rather than per machine. That should do it! Now you have a connection to the git repository/ssh server that knows to always use the correct ssh key on the first attempt, and doing so should avoid the “too many authentication failures” error.The new installation process is much simpler and changes where SourceTree is installed. Now let’s try to clone that Git repository again. This section tells your SSH client that anytime you’re connecting to a host that matches the pattern *.drush.in, use your SSH key named “pantheon”. Open your SSH configuration file in your favorite editor: nano ~/.ssh/configĪt the bottom of the file, add the following information: # Pantheon Use a Specific SSH Key for a Specific SSH Server This involvs editing a text file on your computer that is generally located within the same folder as your SSH keys. All we need to do is modify our SSH client configuration and tell it to always use the correct key with the specific server. If the key you need to use for the server is attempted by your client after the MaxAuthTries as configured by the server, your client will never reach the correct key and will fail its authentication attempt.When attmpting to connect to an SSH server, if you have not told your SSH client specifically which key to use with the server, it will attempt to use all of your keys (one at a time) until it finds one that works.I believe this setting for ssh servers is called “MaxAuthTries”, and the default value is 6 (don’t quote me on this, I am not a sysadmin expert). SSH servers are commonly setup to allow for a maximum number of attempted authentications before rejecting the attempt.This can easily lead to the problem I’m seeing due to the way that SSH servers can be setup vs how SSH clients attempt to authenticate with the servers. If you work on a lot of servers for various reasons (clients), you may have a lot of SSH keys on your computer. That all looked good, so I decided the problem I was running into was one I had faced before… too many ssh keys on my local computer. ✅ That I had uploaded that key to my Pantheon account.✅ That I had an SSH key on my computer for use with Pantheon.Thinking that I may have forgotten to setup my SSH access correctly, I double checked the following things: Please make sure you have the correct access rights $ git clone port 2222:2: too many authentication failuresįatal: Could not read from remote repository. When recently setting up a new website on Pantheon, I ran into a problem with cloning the new site Git repo to my local computer.