Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Git Bitbucket Credential Manager for Windows periodically pops up.

Periodically (every few minutes) the credential manager for Bitbucket/Atlassian shows up when I am running Sourcetree. I can cancel the popup window and go to my authentication options in Sourcetree. I have three accounts connected: two GitHub and one Bitbucket. I use OAuth on all three accounts, but it seems the authentication for Bitbucket expires and I must go through the process of refreshing the token. Neither GitHub authentication tokens expire.

I can refresh my Bitbucket account without any issues, but then it will expire and I will get the credential manager popup within minutes.

1 answer

0 votes
minnsey Atlassian Team Feb 02, 2018

Hi

The Bitbucket access_tokens do expire after 1 hour, GitHub last 1 year. However the Git Credential Manager should be storing a refresh_token which will allow it to automatically get a new access_token for Bitbucket.

Because Bitbucket OAuth support was only added to the Git Credential Manager (GCM) from version 1.10+ I have experienced similar issues where, for example I have files from a Btbucket repository open in Visual Studio Code that is running an older version of Git/GCM that does not understand about refresh_tokens, it can then end up effectively invalidating and wiping the refresh_token, causing the 'good' GCM to have to re-authenticate.

I would double check you are running a consistent Git environment, with Git >= 2.15

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,402 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you