Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


OAuth authentication results in a blank screen and git clones fail


One time is an annoyance. Twice is a coincidence. 3 or more times is a pattern.

We have several folks who cannot authenticate to using SourceTree to obtain a refresh token for git clone/push/pull operations. There experience whether this is a first time setup or the nth is this.

They *are* able to log in to the website fine.

  1. Open SourceTree > Tools > Options > Authentication tab
  2. Add/Edit an account, specifying
    1. Hosting Service: Bitbucket
    2. Host Url: (uneditable)
    3. Preferred Protocol: HTTPS
    4. Authentication: OAuth
    5. Username: blank (uneditable)
  3. Click Refresh OAuth Token
  4. A Browser (often Chrome) opens and they are are required to login if they haven't
  5. Ultimate, they should get a http://localhost:34106/?code=<some-code>&state=authenticated page

For many in our org, that authentication page remains blank.  There are no error messages and it appears SourceTree authenticated until they try to perform a git clone/pull/push at which point they receive the following error:

Error: remote: Invalid credentials

fatal: Authentication failed for '<workspace>/<repo>.git

We have tried clearing cache, windows credentials, updating SourceTree and Git to no avail. The only solution for these folks is to use SSH. But SSH support in SourceTree is terrible.

What is the resolution to this issue?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events