nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Authenticating with Bitbucket not possible

KrisJanssen

I recently tried to set up my dev environment on a new macbook.

Sourcetree 2.4 (90)
maxOS Sierra 10.12.3 Beta (16D25a)

I first tried to authenticate using HTTPS with Bitbucket but even after verifying/resetting my password multiple times, I can just not login, I just get a very random error message:

Could not authorize request with the available token. Please re-authenticate.

To login, I have tried adding my Bitbucket account through 'preferences/accounts'

Screenshot 2017-01-12 15.15.15.png

After supplying my credentials it sometimes briefly loads my avatar correctly, like it does for GitHub but upon loading repository browser, it instantly unloads the avatar and throws the error above:

Screenshot 2017-01-12 15.19.32.png

This is getting very annoying, very quickly...

Moreover, even though I have correctly generated an SSH key pair and added the public keys to my GitHub and Bitbucket accounts, the Sourcetree account UI refuses to 'see' or let me add my keys... it insists on generating new ones. Why is that?

Screenshot 2017-01-12 15.22.45.png

Screenshot 2017-01-12 15.22.54.png

Like this, Sourcetree is effectively useless ...

EDIT

The above issue presents itself when trying HTTPS authentication in combination with OAuth. If instead 'basic' authentication is chosen, repo browser seems to load remotes correctly. However, occasionally I still seem to get logged out.

Screenshot 2017-01-12 15.22.54.png

Screenshot 2017-01-12 15.15.15.png

Screenshot 2017-01-12 15.22.45.png

Screenshot 2017-01-12 15.19.32.png

Accepted answers

All comments

Michael Howell_jrj3nz

I am having the exact same issue.

Jeff Coughlin

I am having a similar issue, but for me it's with github. I was having a similar issue connecting to bitbucket, but was able to get around it by allowing SourceTree to create a new key.

selenetw

I am having the exact same issue.

os：macOS sierra 10.12.3

SourceTree 2.4

Same issue here. It doesn't work for Github OAuth, but Bitbucket is fine.

selenetw

when i change the username , everything will be OK

Chillifish

Same here.

rushko

Same here, no solution yet?

dawidof

Same issue, couldn't authenticate to github.

Siddharth Sudhe

same here! I hope there's a fix soon!

Jack White1

I'm also experiencing this issue.

paullewisn

Identical issue here too.

If I am oauth/SSH I get:

Could not authorize request with the available token. Please re-authenticate.

If I am to basic/SSH I get:

The operation couldn’t be completed. (com.google.HTTPStatus error 401.)

If I am oauth/HTTPS I get:

Could not authorize request with the available token. Please re-authenticate.

If I am basic/HTTPS I get signed in, but I have to re-enter my password twice on each pull or push, despite the 'store in keychain' option being set.

Very close to giving up.

keskinonur11Rename

I tried as you said, before i had the same usernames for my Github and Bitbucket accounts. Then i changed the username of my Bitbucket account and everything works now

keskinonur11Rename

I tried as you said, before i had the same usernames for my Github and Bitbucket accounts. Then i changed the username of my Bitbucket account and everything works now

Dawid Sowa

It's been two months and I still can't connect sad

paullewisn

This is with BitBucket. GitHub works perfectly for me!

keskinonur11Rename

is your Bitbucket and github account names equal? if so change your Bitbucket account name (just add 2-3 more characters at the end) and retry. i solved my problem just like this.

miroslavbucek

Same issue.

Jan Dockx_1xm4s7

me23

alpex92

Same issue here. Fix this please!!! SourceTree 2.4.1 MacOS sierra.

Mark Woodward_y6zbz6

Same issue started happening suddenly for no apparent reason.

"Could not authorize request with the available token. Please re-authenticate."

And am CONSTANTLY receiving prompts to enter BitBucket password, even when there are several prompts already displayed.

SourceTree v2.5 (104)
MacOS v10.12.4 (16E195)

Issue persists after performing the following:

Have removed all accounts from SourceTree
Removed all ssh keys
Removed SourceTree's generated .ssh/config
Removed all BitBucket/Atlassian passwords from KeyChain
Added my BitBucket account to SourceTree again (OAuth)
Generated new ssh key

My BitBucket and GitHub usernames are the same, but I'm not even trying to add GitHub at the moment.

Mike Gorodilin

Same issue. It's getting extremely annoying...

Alvin Cris Uy

Any body solved this issue without changing usernames?

Chillifish

No. Can't understand why there's been no response either.

KrisJanssen

One of the latest builds for macOS seems to resolve the matter finally:

2017-05-26

Actual version no is 2.5.2, build 111

Knock on wood...

bgannin

Hi all,

The addition of OAuth was a fundamental architecture change for SourceTree on macOS and unfortunately there have been a number issues centered around how tokens are stored and accessed in the keychain that we've spent a lot of time investigating for the next update (2.5.2). That release is available here as OSX_Beta_Latest.zip currently with a refresh coming tomorrow (you can sign up for the trusted_testers mailing list to be notified of updates.) Full details: 2.5.2 Release Notes

We greatly appreciate our community's patience as we deal with these growing pains and varying implementation details such as hourly token timeouts or newly introduced rate limiting. Once 2.5.2 is generally available if you're still encountering problems we'd ask that you reach out either via a ticket on JIRA or Atlassian Support, depending on your preferences. Rest assured, we're reading your feedback in all channels and striving to make the product better with each release.

Brian Ganninger
Senior Mac Developer, SourceTree

bgannin

The new build, 2.5.2 (109), is now available as a beta.

unknown

Brian, I've tried the beta version (2.5.2), still doesn't work.

Juan Carlos Picado

Me too.

Juan Carlos Picado

Yes, it worked out.

KrisJanssen

You might havre mentioned that you need to download an early build for things to work.

The officially available 2.5.2 (105) still has issues.

The build that actually fixes things is 2.5.2 (111)

bgannin

Please file a ticket on JIRA (see previous posts) and we'll follow up on debugging details. Thanks for your patience.

haranathg

Hi, I've tried 2.5.3c and 2.6.3a on MacOS 10.11.6 (El Capitan) - and both I'm having issues connecting to bitbucket. Same errors reported by this user both for the oAuth as well as basic authentication. I'm able to connect using the preferences/accounts - but when I tried to refresh the repo I get the errors.

Appreciate any help!

Manju

Hi, Can you please make sure the protocol for the account and your repo clone/remote URL are same?

If account is ssh, remote URL should also be ssh and likewise with https.

I would recommend using the latest version 2.7 (142) for your work.

Thanks,
Manjunath

Sonia

I am having the same issue... I cannot login to Bitbucket in Sourcetree to update my remote repositories. I am using 2.7 on MacOS High Sierra. I checked that the protocol is the same. I tried with OAuth and with the Basic Auth Type. Nothing seems to work. I can login just fine on BitBucket Cloud though, and double checked my username and password. Nothing works... Any help is appreciated.

jtressle

I have the same exact issue.

Has this been fixed yet?

I've reinstalled Sourcetree, cleared all caches, keychain credentials and am still unable to access my remote gits.

My error is " The operation couldn’t be completed. (com.google.HTTPStatus error 401.)"

Manju

Can you confirm the version of Sourcetree you have installed now?

KrisJanssen

This happens even with the most up to date versions of Sourcetree (It auto updates rather frequently): currently 2.7 (152)

ferile-bitbucket

That's what happens on mine as well.

It seems related to High Sierra Mac OsX, and the current version of Sourcetree as of January 2018.

I fixed mine by changing my username on Bitbucket, but I still get intermittent issues around auth and saving my password to keychain.

ferile-bitbucket

That is my issue as well. Same thing

mywebdrag

Hi All, has anyone solve this issue? i'm having the same problem.

will martin_um12fb

As a workaround, when I was awaiting notification from our security team that my access was granted ...

I logged in to SourceTree with my google account.

Then I logged into my repo from within Sourcetree, and no issues.

I *was* having issues with direct bitbucket repo creds against sourcetree.

Since the initial success with my gmail to get into SourceTree, I am using my internal account as desired for all logins.

hope this helps.

jtressle

My workaround was to downgrade SourceTree. I went back to version 2.6.3 (build 134) and the problem went away.

bosenj

The issue is still there, i'm having the same problem.
I feel frustrated. my sourcetree version is 2.7.1.

Mike Rampanelli

Thanks, that worked for me too. I'm done upgrading Sourctree. Too many times I've been burned by bad updates. If it works, don't upgrade.

Mike Rampanelli

Thanks, downgrading to 2.6.3 worked for me too. I'm done upgrading Sourctree. Too many times I've been burned by bad updates. If it works, don't upgrade.

mabeaty

Ugh. This is freaking annoying. I'm going to have to abandon SourceTree.

mabeaty

Latest version as of today. Can't sign in to my bitbucket repos

Mike Rampanelli

I'm evaluating Git Tower and so far it's pretty good. It's not free though.

mabeaty

This is maddening. It was working without any changes to SourceTree or my bitbucket account. And then it just stopped working. I can't push or pull via SourceTree. Sure, I can use the command line, but I like the UI. I'm not sure Atlassian cares if people abandon SourceTree because this problem continually pops up just out of the blue, people complain, and nothing gets done other than to tell people to jump through hoops to fix a problem they can't seem to figure out.

stefanbauwens

Changing my account protocol from HTTPS to SSH in Preferences > Accounts solved this problem for me.

rob1702

Thanks for this, I was on SSH and changed it to HTTPS and managed to login. Then I changed it back to SSH and it works fine.

bgannin

Hi everybody,

I'd like to start by saying we hear your feedback and understand your frustration. We know how serious this is and apologize for the pain caused by these bugs.

We're a small but dedicated team in Atlassian doing our best to balance everyone's needs. When something like this happens we are keenly aware of how we failed you and know that we need to, and will, do better. Now let’s dig into some of the details and provide clarity around issues for this topic.

Several moving parts affect the authentication processes in Sourcetree for macOS:

   • OAuth tokens that have differing expirations and requirements per hosting service 
   • Classic HTTPS username/password challenges 
   • Two factor authentication 
   • SSH keys (user managed or ST managed) 

The following external changes also had an impact:

• macOS revising how SSH keys are loaded and managed in 10.12 and 10.13 (details) 
• GitHub deprecating and disabling 'weaker' TLS encryption (details) 

That complexity is our problem to solve though and you count on us to do it while delivering a rock solid experience, period.

To make tracking down issues less painful we've opened up our internal auth logging via the new Debug menu in 2.7.2. We are dedicated to improving this area, with fixes present in every release since we first started expanding the authentication options. Each sprint includes dedicated time to review and investigate any new authentication reports with test builds often privately shared with those affected.

Filing a ticket (https://jira.atlassian.com/browse/SRCTREE) is the single best way to help out. We review every ticket for how it impacts Sourctree, determine if it’s an existing or duplicate issue, and then follow up if we need more information or clarity.

Beta content, especially bug reporting, is not discussed or triaged on Community because this forum is for public releases - anything related to betas should be discussed on the "Trusted Testers" mailing list (https://groups.google.com/forum/#!forum/atlassian-sourcetree-beta) and/or tickets per the introductory message.

We genuinely want your help when these issues arise. Please vote or comment on an existing ticket; if there isn't one, open a new ticket with as much detail as you can provide. This will help us attack the right problems as fast as we can.

These are the primary tickets we're tracking for future updates:

   • SRCTREE-5368 missing uuid (fix deploying in 2.7.2 beta 4 today) 
   • SRCTREE-4544 multiple prompts for SSH Keychain password 
   • SRCTREE-5372 multiple password prompts with HTTPS 

Thank you for your feedback, patience, and tickets - we strive to make our apps better every day.

Brian Ganninger
Senior Mac Developer, Sourcetree

Mike Rampanelli

Thanks for your response. One note - 5372 either doesn't exist or the general public doesn't have permission to view it.

bgannin

Good catch, fixed.

Matt Gregg

I'm on version 2.7.3 (169) and was trying to revert from OAuth to Basic auth and the dialog hides the password field so you can't even enter your password. I got around this by tabbing from the username field to the hidden password field and pasting my password.

Manju

Is this on Basic auth + ssh configuration for account?

JoshFialkoff

Hi @Brian . Is this solved? I'm stilling getting errors. See: https://community.atlassian.com/t5/Sourcetree-questions/Getting-quot-Could-not-authorize-request-with-the-available/qaq-p/708633#U915415

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree

bitbucket-cloud