CODEWITHSUNDEEP
gitvisual-studioazure-devopsvisual-studio-2019
NotFound
NotFound

Reputation: 6102

GIT Fatal error: Authentication failed in Visual Studio

As of today I'm getting errors when trying to use git commands with my repository in Azure-DevOps. The repositories sit in a project on DevOps that I can access with the same account and shows no sign of any recent changes to it. The steps I can take to reproduce it is:

  1. Open the command prompt and enter git fetch
  2. A window appears prompting for a login Login
  3. I click the account
  4. No password is prompted, but an e-mail arrives that a PAT has been created
  5. The command prompt yields an error

Error:

fatal: Authentication failed for `<link to repository>`

Things I've tried so far:

Currently running:

Edit:

I've attempted using Visual Studio Code with the Azure Repos 1.149.2 extension and get the same error. It yields me the Microsoft page to enter my code for device login which it grants, but using git commands give me the same error messages.

I've also had my profile removed from the Azure DevOps environment and re-added without success.

Upvotes: 18

Views: 63025

Answers (8)

Miri ST
Miri ST

Reputation: 1

I was having a similar problem in Visual Studio for Mac 2022. It was my first time installing VS on my Mac and attempting to clone a repository to local, and the first time I tried to do so I mistakenly entered my password instead of my Personal Access Token. I fixed it by going to Keychain Access, searching for "github," selecting the one with the time that corresponded to when I had tried to clone the repo, and changing the password to my PAT. The next time I attempted to clone the repo, VS asked me if it could use the item within Keychain Access, and I granted permission and it worked.

Relevant GitHub docs: https://docs.github.com/en/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain

Upvotes: 0

Gul B
Gul B

Reputation: 41

I also faced this issue. This is what worked for me.

  1. Navigate to windows credentials: Control panel (cpl)-> user accounts -> Windows credentials-> Generic credentials Screenshot of Windows credentials

  2. Locate the url you have issues cloning (under Generic credentials), it will be prefixed with git: and remove that entry and close the control panel. Screenshot of Remove entry

  3. Close Visual Studio (if open) and reopen and try to clone now, Visual studio will prompt for credentials.

I hope that helps. :)

Upvotes: 3

frmbelz
frmbelz

Reputation: 2543

The same error (Windows, Git Bash command line, Visual Studio, bitbucket). Using https (not ssh) which should prompt for login credentials but instead errors (likely because my bitbucket credentials changed):

$ git pull origin master
fatal: Authentication failed for 'https://bitbucket.../my_git_project.git'

$ git config -l
...
credential.helper=manager
...

$ git config --global --unset credential.helper
$ git config --system --unset credential.helper

git pull now prompted for username/password prompts.

Upvotes: 0

MisterA
MisterA

Reputation: 83

I had a similar problem in VS2019, I moved laptops and it refused to authenticate despite me deleting and changing the credentials using credentials manager. I'm linked to a repository in Assembla and In the team explorer window under repository settings I noticed that there's a tick box to override the global user name and email settings, which were different from my Assembla login.

Upvotes: 1

SouthShoreAK
SouthShoreAK

Reputation: 4296

I had the same situation - everything worked in VS 2017, but 2019 would not work. I found this article, which suggested I update the Git Credential Manager for Windows. My installed version (at C:\Program Files\Git\mingw64\libexec\git-core\git-credential-manager.exe) was 3 years old. Downloaded, installed, and the problem went away for me.

Upvotes: 4

NotFound
NotFound

Reputation: 6102

In my particular case after many mails back and forth with Microsoft it turned out that two of my accounts somehow started conflicting with eachother causing weird errors. A nice example was that making changes to a wiki in DevOps would show a different account in the commit trial than the account I was logged into.

In the end Microsoft managed to fix it and I haven't had any issues since.

Upvotes: 2

jessehouwing
jessehouwing

Reputation: 114461

To force the Git credential Manager to stop interfering, you can add the following to your global git config:

[credential]
    helper =

This effectively turns off any credential manager. In Azure DevOps you can then configure a set of Git Credentials or a Personal Access Token and use that to connect directly.

It doesn't explain the problems you're experiencing. Given that your account seems to be Machine Bound and an AAD account a lot of things can be in play. This includes AAD Home-Realm Discovery and Single Sign-on and Azure Active Directory Guest accounts.

Another possible problem is your Windows Credential Store which has multiple locations where Azure DevOps and Git credentials are stored. And finally the account used to sign-in to Visual Studio 2019 to retrieve its license may be playing up.

With the information you've provided it's neigh impossible for us to help you resolve the issues without looking over your shoulder. I'd almost suggest filing an Azure support request if you have them available so an engineer can look with you.

Optionally run

git-credential-manager.exe erase

And pass in the following data

protocol=https
host=dev.azure.com
path=/jessehouwing/vsts-extensions/_git/vsts-github-tasks
{newline}

To tell git to delete the credentials stored for your account

Upvotes: 12

VonC
VonC

Reputation: 1323115

Try and check the value of git config credential.helper.

If you see "manager", open the Windows Credentials Manager, and put as a password the PAT -- the Personal Access Token created -- (while keeping your regular login, associated to the remote URL)

Then try again, and see if the issue persists.

Upvotes: 13

Related Questions