My company has a security policy that blocks an account after more than 3 failed login attempts.
I have a lot of repositories that were using the same old stored credentials, and now that I've changed my password if I attempt a pull before changing the credentials for the repository I get my account blocked because Sourcetree always attempts to authenticate 4 times.
How I can set Sourcetree to attempt only once?
Hi @renecum_cignium,
You can't change this directly. I recommend changing your authentication settings for each repository by deleting the Keychain entries and letting Git prompt you again for them. Or simply cloning fresh if there are no local changes. Hope that helps a bit.
Brian Ganninger
Principal Developer, Sourcetree
Hi @bgannin thanks for your reply but this doesn't help much. I have about 45 repositories, and even after I have deleted my keychain credentials some of the attempt to authenticate when I open them in Sourcetree and my account is blocked again.
How can I add a feature request to fix this?, This is not the first time that I need to change my password, every three months I got the same problem since we are forced to change the password once every three months.
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.
Has this been addressed yet? I am in the same situation at my company... three login attempts and I'm hosed.
The solution sounds simple enough in theory, but gets complicated in a hurry when using a number of different machines (like I do). If I forget that one of the machines has not been updated with the new password, then the next time I use it... BAM! And now I need to update all my repos on this machine with the new password, and also the repos on all of my other machines as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This needs to be addressed. Using AD authentication, it can't just keep spewing failing login attempts, as this locks accounts quickly!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there, one thing that I've done to 'fix' this was to uncheck the option 'Check default remote for updates every 10 minutes' in Tools -> Option -> General tab. It seems to have avoided this issue.
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.