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
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'm trying to setup a new machine to use as a build server.
It needs to be able to do pulls from bitbucket.org for the project its building.
I have an apppassword setup and that is being used however _every_ time I do a pull, clone etc the stupid window asking me to log in to your account pops up. I can click on the browser option and it says I'm already logged in, I can click on the password option and enter the apppassword.
No matter which option I use the next time I go to do a pull etc its back - WHY?
I've tried deleting the entries in windows credential manager, it just recreates them but seems to pay no attention to them.
This is totally unusable for a build server - its meant to be start the build and let it run, not have to constantly check back to see if there is a random prompt. This works fine on the existing machine just not on the new one.
Hello @Paul James and thank you for reaching out to Community!
Git by itself does not cache credentials for authentication and relies on other tools, usually called credentials managers to store your credentials and use them in subsequent git commands.
From your description, it seems like you are using Windows, so I would suggest confirming if you have installed the latest version of Git For Windows, which already comes with Git Credential Manager installed (GCM).
If you have disabled the installation of GCM when you installed git, you can manually download and install GCM following the instructions in this documentation.
Once GCM is installed, the next time you execute a git operation, it will prompt you for the credentials and then save it on GCM cache. For any subsequent git command, git will get the credentials from GCM cache and you will not need to provide it again.
You can confirm that git is configured to use GCM by using the following command :
git config --get-all --show-scope --show-origin credential.helper
This should print what is the current credential helper configured in your system at multiple scopes (local, global, system). If GCM is installed in the machine, we would expect the output of this command to return managed.
Also, it's important to note that according to GCM's documentation related to Bitbucket Authentication :
If you are planning to use an App Password for basic authentication, it must at a minimum have Account Read permissions (as shown below). If your App Password does not have these permissions, you will be re-prompted for credentials on every interaction with the server.
So could you please confirm if the app password you are using contains at least the scopes shown in the image?
Let us know in case you have any questions.
Thank you, @Paul James !