The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
- Community
- Q&A
- Sourcetree
- Questions
- How does Sourcetree/Atlassian team plan to deal with the transition of no user and password?
How does Sourcetree/Atlassian team plan to deal with the transition of no user and password?
I got the following email a couple of weeks ago:
| ||
| You are receiving this email because our server logs indicate that you have used your Atlassian account password when using Basic authentication with: | ||
| ||
| Beginning March 1, 2022, you will no longer be able to use your Atlassian account password when using Basic authentication with the Bitbucket Cloud REST API or Git over HTTPS. To avoid disruption, we recommend that you switch to a Bitbucket Cloud app password as soon as possible. |
However, you can only clone a repo if you have a user and a password? Is this going to be fixed? Because right now it's a bug in Sourcetree and I cannot download my new repos or update any.
Thanks.
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian