You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
G'day Shweta!
Thank you for contacting Bitbucket Cloud Support.
The most common issue customers are experiencing related to authentication is due to the deprecation of GIT username/password in favour of App Passwords on 01/03/2022:
https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231
You will need to make use of an AppPassword for communicating to GIT via HTTPS.
We have documentation for usage of app passwords at the following link:
https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/#Create-an-app-password
Essentially, when connecting via HTTPS you will use your AppPassword alongside your username seperated with a ":" character.
Therefore if you are authenticating to GIT over HTTPS to push/pull you will need to update your remote URL's to include the AppPassword:
git remote set-url origin https://USERNAME:APP_PASSWORD@bitbucket.org/username/reposlug.git
The same applies when performing git clone:
git clone https://USERNAME:APP_PASSWORD@bitbucket.org/username/reposlug.git
Hope this helps.
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.