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. 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.
#AUTHENTICATION FAILED SOURCETREE UPDATE#
With this update you'll no longer need Admin rights during installation, so the update process will be much less intrusive.
Moving the installed location from %ProgramFiles(x86)%\Atlassian\SourceTree to %localappdata%\SourceTree means SourceTree is installed per user, rather than per machine. The new installation process is much simpler and changes where SourceTree is installed.
0 kommentar(er)
