invalid credentials remote: Bitbucket Cloud recently stopped supporting account passwords for Git authentication. remote: See our community post for more details: https://atlassian.community/t5/x/x/ba-p/1948231 remote: App passwords are recommended for most use cases and can be created in your Personal settings:
After spending way too much time on this, it dawned on me that it's just the password that needs changing. The username is the same. Was fooled by the fact that I had to name the new app password and mistook it for a username....
It seemed pretty ok for me. I followed this page from when I was getting notices when pushing my work to BitBucket. I created my App password which kind of works when adding my created app password as my new git password through SSH
"hey @paulbcon2426, I was wrong when I said you shouldn't be seeing this UI. This most likely a part of your Git credential helper configs (more details here). Given this is asking for credentials during Git over HTTPS authentication you will need to be using your app password. Can you please let me know if it works with an app password"
@David Dansby When I removed the remote vpusa, it works, my problem now is how can I set it up to push to another remote url simultaneously?Can I just use the same app password and it will push to both remote urls?
I access my passwords through different computers however, it is not necessary for me to ask for the second computer, second computer, it is not necessary when using the password for the first time on my second computer. How can I proceed with this?
Note: on my personal computer, an application confirmed by the application was saved and it doesn't ask me again when you pull/push, however, on the second (work) pc it always asks me for the password.
caso tenha ficado mais alguma duvida de não terem conseguido fazer o clone entre no site https://bitbucket.org/account/settings/app-passwords/ -> Create app password -> pode usar qualquer nome "teste" por exemplo -> aceite todas as permitons, após criar vai ser gerado a senha para usar no git clone
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2022 edited
@Ivan Lott I would suggest a password manager. That's what I personally use for my personal Bitbucket Cloud account. That way I don't have to remember my app passwords and I can sync my password manager across computers.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2022 edited
@paulbcon2426 you should be able to set up the dual push to remote again with vpusa. So long as you still have write perms to the repo you are pushing to (i.e. you are allowed to push to the repo) then your app password will allow you to still push to both remotes.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2022 edited
@Mert the README for the repo it appears you just need to create an app password to use for the BITBUCKET_APP_PASSWORD variable. This community post should guide you to be able to create an app password that'll you use for it
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2022 edited
@Ivan Lott for the case you want to just push to your Bitbucket Cloud repositories from different computers then you should only really need 1 app password; the username tied to it would be your Bitbucket Cloud username. However, you could technically make multiple app passwords and store each one on each different computer. THe main reason I recommended a password manager in your case is so that you don't have to remember the app password (because it won't necessarily be stored in every git credential manager on each computer you use; you may have to add it on each new computer you use) when you move to different computers.
Sometimes its easier to think of an app password like a normal password but you are able to see when it was last used (in the app password settings), you can revoke it easily (also from app password settings), and you can attach different privilege scopes to it (for example, you could have one that is only used for pushing/writing to repos, one for just pulling/reading from repos, and maybe another one used for pushing/pulling snippets). For my personal use, I like to use 1 app password for pushing and pulling; but if I forget it and I'm on my Bitbucket Cloud account on a new computer its also easy enough to make another app password to push/pull on that computer and than if I don't intend on using that computer again I can always revoke that specific app password (in your app password settings in your Personal settings) so you don't have to worry about removing it from Git credentials on that computer you temporarily used it for.
@David DansbyOhh I understand, so i will try to do what you explained to me, anything i will get back to you here. Thank you very much for your attention.
@David DansbyIs it normal, on my secondary (work) computer, every time I do a push/pull, I'm asked for the password? this is my doubt now, because on my personal computer, this request doesn't happen every time I pull/push. And sorry for my english, I'm still learning and I'm using the translator to write here hahahah
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2022 edited
@Ivan Lott No problem with your english, it's good actually. I believe the issue is that your work computer's Git config doesn't have a git credential manager storing your password so that you are being asked time to enter it. What OS/computer type is your work computer? I ask because your computer may have a credential manager that you can use to store your password (Mac uses oskeychain which stores your credentials as encrypted).
You could also use the "git-credential-store" to store your password (details here) but the only thing is that it stores your password unencrypted on the disk. However, if you make an app password specific to your work computer for just pushing/pulling to repositories then it may be less of an issue given you restricted the privilege scope of the app password and you can revoke quickly if you need to; but security-wise it's still something to be aware of.
This change is a major break in feature for Bamboo Server. Any linked repo with using the Bitbucket Cloud as the Repository host type are no longer working. Any PRs or branches are now unable to get build status from Bamboo.
Event though the general GIT repo has a Bitbucket Cloud web repository option, it does not push statuses.
I do not know how to search through comments to see if anyone has brought this up.
283 comments