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
I have a user who is showing 2 Bitbucket accounts. This user is having issues cloning repos. He get prompted for username and password and can never get past the prompt even though he's using the same credentials he used to login to Bitbucket. Looking at his account I see the following:
There are 2 Bitbucket accounts. Where all the other users look like:
Just 1 Bitbucket account.
How do I get rid of the second account on the above user? I assume this is what's causing the issue with him not being able to clone because of incorrect credentials. When cloning, i.e., git clone https://user@bitbucket.org/nocccd/some_repo, he gets a prompt for credentials which gives invalid credentials.
Am I correct in thinking the 2 Bitbucket accounts are causing an issue? Any suggestions on how to fix it? Thanks!
I can't give you the exact reason this is happening, but we've solved similar problems before by creating an Application Password and using that password when prompted for authentication. Have the user visit this page this page. Good luck!
G'day!
I agree with the reply from @Blue Ridge Consultants - this prompt is as a result of a change introduced to improve security by phasing out username/password authentication over HTTPS:
https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231
Essentially, they will need to follow the linked application password documentation above to create an App Password for authentication.
When they are connecting via HTTPS, they will need to use their App Password alongside their username seperated with a ":" character.
Therefore if they are authenticating to GIT over HTTPS to push/pull they will need to update their remote URL's to include the App Password:
git remote set-url origin https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git
The same applies when performing git clone:
git clone https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git
I would suggest ensuring that they also ensure that all stored passwords related to authentication over GIT are cleared from their machine (ie Credential Manager for Windows, Access Keychain for Mac or /etc/shadow folder for Linux).
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.