Sourcetree Oauth Github

  1. Sourcetree Oauth Github Free
  2. Github Sourcetree Personal Access Token

Connect to your Bitbucket or GitHub accounts securely and with ease in the latest versions of SourceTree for Windows and Mac. These versions of SourceTree fully support OAuth 2.0. Users with Two-Factor Authentication (2FA) enabled can connect to both services via OAuth and be guided through the standard two-factor login flow.

Now, you can click 'Clone' to clone one to your local machine. I'll clone the 'My-First-GitHub-Site' to my local machine with SourceTree. Cloning a Repo to Your Local Machine. Click the 'Clone' link next to 'My-First-GitHub-Site' (or the repo you'd like to clone) Source URL: (Leave this at its default. If you change it the clone won't work.). From Sourcetree, open the PuTTY Key Generator dialog by going to Tools Create or Import SSH Keys. Click Load, navigate to your SSH folder, and click the private key. Make sure you're looking at All files if you don't see your private key. Fix GitHub API integration, problem was caused by API v2 being removed on github.com; Note: SourceTree now uses GitHub API v3, which currently does not appear to support listing watched repositories (outside of your user / organisations), so these will no longer be listed. SourceTree 1.4.4 Maintenance release Enhancements. OAuth2 framework for macOS and iOS, written in Swift.

  • Status:Needs Triage(View Workflow)
  • Resolution: Unresolved
  • Fix Version/s:2.5.2
  • Labels:
  • Environment:
    Hide

    OS

    SourceTree

    2.5.0 (104)

    War thunder f2h

    Show
    OS uname -a Darwin ev-m-jh.fritz.box 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64 SourceTree 2.5.0 (104)

I could reproduce this error/bug in SourceTree for a different setup (also still valid for 2.5 (104)):

  1. Take an GitHub account with username xyz
  2. Create an OAuth Authentication with username xyz and the same key
  3. Repeat the step above for Bitbucket also with username xyz

Result: the authentication will always fail for the second account added with the following error log:

It seems as the key for the account is somehow related to the username, instead of the username and a unique account id.

Any comments on that?

is cloned from
Oauth

SRCTREE-4708Accessing GitHub and Bitbuckt via OAuth with same username fails

  • Closed
Votes:
0Vote for this issue
Watchers:
2Start watching this issue

Today we are deprecating a Sourcetree-specific portion of the Atlassian Account sign-in API and it will be unreachable after 16 Oct 2019.

One year ago we shipped an all-new onboarding experience in 3.0 for both Mac and Windows powered by a Bitbucket login in your default browser. Prior to that, in early 2018, we tweaked the in-app registration process on Mac to use a new endpoint provided by the Atlassian Account team to achieve a more seamless experience. We are now migrating users away from this individual endpoint as it will allow their team to deliver a better Atlassian Account experience overall.

Mitigation

  1. Download and install the latest release of Sourcetree for Mac.
  2. If you are unable to do so for any reason, download an applicable 2.x release and then perform the following steps in Terminal to setup prior to launching the app:
  • run defaults write com.TorusKnot.SourceTreeNotMAS agreedToEULA2 YES
  • then defaults write com.TorusKnot.SourceTreeNotMAS EmailHash DeprecatedEndpoint2019
  • finally defaults write com.TorusKnot.SourceTreeNotMAS completedWelcomeWizardVersion 3

Impact

Sourcetree Oauth Github Free

There is no impact to existing installations of Sourcetree for Mac.

Github Sourcetree Personal Access Token

The following Sourcetree for Mac releases will require mitigation as noted above:

  • 2.7
  • 2.7.1
  • 2.7.2
  • 2.7.3
  • 2.7.4
  • 2.7.5
  • 2.7.6

Note: The registration and Atlassian Account portion of the Welcome Wizard will no longer complete after 16 Oct 2019.

To discuss this or any other Sourcetree topic please visit Atlassian Community.