Just tried to PULL my repository with SourceTree setup to use oAuth. Created an app password in Bitbucket.org and set my sourcetree authentication to basic with my existing username and app password. It authenticates in the setup when saving but when i pull I still get the notification that Bitbucket Clouse recently stopped supporting account passwords for Git authentication and recommends app passwords. I have exited SourceTree and restarted and still get the error. Any help would be appreciated.
What a joke. I did not managed to pull repo with sourcetree using new app password. It was working fine from console but not from sourcetree. Anyway installed Fork and works like a charm.
Hi @David Dansby , following your advice, I talked to my superior, and I decided to do the following, with his approval too, to use a password on my personal computer and a different password on my work computer. So I used the option git remote add auth-origin https://user:password@bitbucket.org/seu/repositorio.git and that way I left it defined on each of the computers so they don't keep asking for the password again at each pull/push. Anyway, thank you very much for your attention and explanation. I managed to solve the problem as best we could. Have a nice weekend and God bless you.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2022 edited
@Kennedy can you please provide more details so I can try and assist you. Did you update the connected Bitbucket Cloud repository's credentials? username should be the bitbucket username and password should now be the app password
I'm having issues accessing my projects through git. It looks like my SSH key was deleted and i needed to enable pipelines. I did that and added my key in, but it's still not working! I also tried cloning with https and that is failing too! What is going on!
Totally unwelcome change, I am moving all my repos away. You are out of your mind if you think I am going to generate app passwords for the 5+ different devices I use every week. If my single password falls into wrong hands, I will just reset it. Easy as that. Bah.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2022 edited
@立差西 Please do not post any credentials to Community. I have removed your previous post to this thread because it contained what appeared to be either an password in cleartext. I recommend that you change your account password and revoke that previous app password for the sake of your own security.
There is a known issue in regards to Windows edition of SourceTree whereby the git credential manager can sometimes can hold onto the previous credentials instead of using the new credentials. In which case it might be necessary to uninstall sourcetree and then navigate to c:\users\<your user ID>\AppData\Local\Atlassian\Sourcetree and rename/delete the passwd file found there. At which point you can then reinstall SourceTree and generate a new app password to use instead.
We have a bootstrap script, which is build to configure a new server based on the repos it pulls, and set up auto-pull scripts to keep the local versions up to date. The autopulls have all been adjusted by editting the .git/config in each folder to use the app password, and those work. Our bootstrap script, however fails to work at all. We have added the app password to it, but when trying to use this command, instead of downloading the file in question, we get an Atlassian HTML "Something went wrong" page in the place of the file we are trying to download but using the file's name. (in this case base.psm1 is still the name of the file, but its contents are your html stuff)
# Download Base Module to start things off (need my modules) New-Item -ItemType Directory -force "$scriptsRoot\libs" ; # make libs folder $webClient = New-Object System.Net.WebClient ; $webClient.Headers.Add( "Authorization", "Basic {0}" -f ([System.Convert]::ToBase64String([ System.Text.Encoding]::UTF8.GetBytes( $bbCredentials ) )) ) ;
I assume, the problem is that we are using Authentication "Basic {0}", but I have no idea what should go in there now. Will this command even work, now that App passwords are required?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2022 edited
@Hein Thu Ya can you provide more details so I can try and assist you with your issue. What privilege scops did you select for the app password. Are you using your Bitbucket Cloud username as the username during authentication or are you using your email? As noted in the docs and this community post, email address as username is not allowed when using app passwords for authentication.
Once you provide more details I can hopefully get your issue resolved.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2022 edited
@Jon Mckeever I don't fully understand your issue. However, now when interacting with the Bitbucket Cloud REST API (and Git over HTTPS protocol) Basic authentication is only allowed with app password. Please note, that the username for app password authentication only allow Bitbucket Cloud username as the username. Email address is not allowed for username when authenticating with app password.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2022 edited
@wall-e to be clear, there is no requirement that you have to create a separate app password for each device. You are fully allowed to create just 1 app password and use the same one on all your devices.
From a security standpoint, one of the good things about app passwords is, if someone gets your one app password (that you may use on multiple devices you easily revoke it from your personal settings) without having to go through the steps of resetting your account password and worrying if someone accessed your account with your account password before doing so.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2022 edited
@Adam Hughes thank you very much for that very helpful guide for JetBrains IDE users (the same steps should be allowed on most, if not all, JetBrains IDEs).
For clarity, you were one of the "lucky" ones that were a part of the later stage of the %-based rollout :). We don't do full, single rollouts with large changes like this; it allows us to catch any potential issues before they could affect everyone. If you are interested, this is actually a good blog post explaining how we do rollouts for large changes (it's old but still relatively applicable; also note, it's a transcript of the original recorded video during a meetup).
283 comments