Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

authentication broken no idea wherer to start.


I'm not much good with git, or how it works, it just works (well normally). I have a repo on bit bucket and I can log in ok.

I also set up a git client to check in my source code and recently when I push, I get a password prompt. I guess it changed... but the one I use for bitbucket does not work. 

my config says to use a name @ url


but the login to bit bucket forces an email, so I wonder if something changed on the bitbucket end? I tried removing the name and logging in with the email but that too is failing.

Maybe the accounts are out of sync? If I put in this url to a browser, I log in ok.





2 answers

0 votes
Patrik S Atlassian Team Apr 27, 2022

Hello @ulao ,

Thank you for reaching out to Atlassian Community, and great to hear you were able to get it working!

First of all I'd like to let you know I've edited the description of your question in order to remove some sensitive information, such the repository and workspace names and also your bitbucket username.

Also, to give you some background on the issue you were facing, Bitbucket cloud has recently deprecated the usage of account passwords for git activity over HTTPS and calls to Bitbucket API, and you should use an App Password to authenticate for those scenarios. You can find more details about that change in the following article : 

So in summary, to login to Bitbucket website you will continue to use your e-mail address and account password, but for git activity over HTTPS (cloning/pulling/pushing) you will have to use your bitbucket username (not e-mail address) and an App Password with the required privileges.

Hope that helps to clarify. If you have any questions or concerns let me know :)

Thank you, @ulao !

Kind regards,

Patrik S

Well I got it working, I saw this encrypted url in my log that said something about an app password.  I followed it and it asked for something like 100 permissions, so I just checked them all. I hit created and it gave me a last pass like generic pass word string. That worked to commit, then I was locked out of this page and my bitbubket .  I then had to reset my password and that let me back in.


both are now working... so not sure what I did there, quite a circus to be honest. I get being secure, but what good is it if uses need to do all of this to log in? I could quite easily see people losing work and wasting lots of time. 


I'd suggest you make this a bit more clear to users at some level, this was not a fun experience.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events