David Dansby Atlassian Team

@Chris Astles can you please provide me with more details so I can try and assist you. When in IntelliJ are you trying Git pull from inside the terminal in IntelliJ? Are you sure you are using a new app password with the correct perm scopes? You created the app password in your Bitbucket Cloud account's Personal Settings,…

@David Shapira that is great to know. Thank you for patience in my assistance on resolving this issue. Also, thank you for taking the time to follow all the steps up through reinstalling in order to get a resolution. I personally know how annoying it is to reinstall software to get a fix, so I really appreciate your taking…

@Jay Wolberg that is good to know. @Luciano Allegro I've been told that credential managers in windows have been big problems for Sourcetree in the past. I don't know if it's specifically related, but I imagine it is so. Unfortunately, right now, it appears the only way to resolve this issue is with a full reinstall using…

@hogtownrocketsled and @yeisson72 and @Jay Wolberg given you all three are still experiencing this issue. I would advise reinstalling Sourectree according to the instructions I have stated above. Another Sourcetree for Windows user noted to me in our community post that this was the only way they got their Sourcetree to…

@Jesus Barrio I also wanted to warn you that this VS Studio Bitbucket extension is not owned by us and from my research appears to not be maintained anymore. For such unmaintained extensions I would exercise caution in using them as they may potentially have more issues out of our scope in the future.…

@_JK_ Kalenowsky we had already updated our community post a couple of days to include a link to the documentation detailing the differing privilege scopes for app passwords under the "Why are we making this change?" section. You can find that documentation here. Please note, this documentation is in our REST API…

@Clemens Wendt sorry for the disruption. For clarification, the email we provided Monday, February 28, 2022, was not the only notification of this change we sent to customers. We have been notifying customers on multiple channels starting in September 2021 via blog (in September 2021), multiple emails (starting in November…

@Jesus Barrio this is most likely related to the removal of account passwords for Basic authentication with Git over HTTPS and API. You can find more details in our community post below. https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231

@Jon Mckeever and @Marc Reig as is common practice with software feature releases, we often do staggered rollouts. So, in this case some users could potentially be able to use their account password for a couple of days after the official March 1, 2022 date. This appears to be the scenario both of you experienced. However,…

@David Shapira @yeisson72 @Luciano Allegro please see my comment above about ensuring your git remote URL uses your Bitbucket Cloud username and NOT your email that is tied to your Bitbucket Cloud account.

@hogtownrocketsled can you please tell me what your git remotes URL state as. I forgot to mention that app app passwords don't allow email as a username and sometimes git remote URLs include the username as the email instead of your Bitbucket Cloud username. One user with a similar issue resolved it with If your git remote…

yes @yeisson72 SSH should work as expected given this change had no impact on SSH authentication. However, some of our users prefer to use HTTPS authentication for various reasons. You stated that you changed your password for a new one. Can you please confirm that you changed this "new password" to an app password which…

Thank you @Alexander Higgins !!!!

@Luciano Allegro just so I verify. You are not receiving the same error as @yeisson72 is, right? Even when you update your app password you are not seeing Sourcetree telling you Authentication is ok but then you still receive the error messaging saying you can't use an account password and to check our community post like…

@Beneris unfortunately, Bitbucket Cloud does not have signed commits. You can still sign your commits, but unfortunately, you cannot add them to your Bitbucket Cloud account. For reference please see https://jira.atlassian.com/browse/BCLOUD-3166

@Fabio Goncalves thanks for the suggestion. Unfortunately, that only pushes the auth protocol for Git to use SSH (which does not require an app password). For various reasons, a number of our users prefer to use HTTPS for authentication which now requires an app password, not an Atlassian account password, to authenticate…

@4dmacau thank you very much for that great update about how to resolve this issue. Can I ask, are you on a Windows machine? Also, were your two teammates that didn't have this issue using Mac? Thanks again

@yeisson72 I don't believe your issue is the same as Allegro's, as they would be receiving the same error message as you if that was the case, and it does not appear that they are. However, I'm curious, are you using Sourcetree on Windows or Mac? Also, did you go to your Sourcetree settings, navigate to the Bitbucket Cloud…

@Luciano Allegro what perm scopes did you select for the app password you created?

@Mrunmayee Prakash Shirodkar if you are still receiving this error in Sourcetree then Sourcetree is still using your account password, not your new app password. Without knowing more, I can only guess a solution. However, you most likely need to change the password that Sourcetree is using. I believe you can do this by *…

@Renee Dubuc you can find more details about app password perm scopes in our API documentation. These are the same perm scopes used for app passwords. https://developer.atlassian.com/cloud/bitbucket/bitbucket-cloud-rest-api-scopes/ I've added this to the main post as well. Thank you.

@Marc Reig have you tried any Git ops (i.e. push/pull/clone) without GitHub Desktop (just using terminal instead) for those shared projects to see if it works fine without GitHub Desktop? 

@Kevin Matlock definitely agree! We are grateful for updates on resolutions you have found as it can definitely help others that may be experiencing similar issues. Thank you very much for that.

@Kevin Matlock thank you for the update. I was actually just about to respond. We haven't experienced this issue on our side testing with Sourcetree. I'm glad you got it working. To clarify, the Firewalls you reference on specific to you (or your company), correct?

@beef623 I can personally relate to your frustration but we (i.e., Bitbucket Cloud) believe this change is necessary for the overall security of our users in order to protect against credential scanning attacks. TBH, I have some of the same concerns/annoyances as you with regards to dealing with app passwords for my…

@rhinor the answer in that StackOverflow discussion is along the right lines, so I'm curious what is still the issue. You may be missing a step or too (the answer provided in there wasn't the most detailed). I see that you are using a Macbook, so the following is trying to closely align with Mac OSX. Can you please tell me…

@svenbader I can say with 100% confidence that the issue you experienced is completely unrelated to this upcoming change. Also, to clarify, the issue you experienced is related to pushing, not committing. Furthermore, testing is never done on production servers. Based on the error message you provided and without knowing…

@svenbader this change has not been implemented yet, so the issue you are experiencing is completely unrelated. Committing on your local machine/directory is unrelated to Bitbucket Cloud. Are you trying to commit in Bitbucket Cloud itself or your local machine/directory? We have not seen/heard of any issues with committing…

That's great!!! FYI we just posted a community update with more details about this change and a corresponding FAQ. I would suggest checking it out even though you got your issue resolved. https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231…

Hi Damien, My name is David and I'm an engineer on the Bitbucket Cloud team. When you are using your terminal in VCS you are not actually using the VSCode version control system (VCS) extension/plugin system that VSCode uses (and for which you authenticated in the OAuth authentication page to integrate with Bitbucket…