Git authentication fails for Azure DevOps Server on Windows

[sdebruyn]

• VSCode Version: 1.95.2
• Local OS Version: Windows 10
• Remote OS Version: Debian bookworm
• Remote Extension/Connection Type: Containers

Logs: git authentication failed

Steps to Reproduce:

1. git fetch

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: No

We have an Azure DevOps Server hosting our git repositories. From what I understood the authentication to AZDO Server happens through NTLM.

I've created a DevContainer while working on my MacBook and everything worked fine.

Now a colleague on a Windows domain-joined machine was trying to work inside the DevContainer but git authentication just fails. Git authentication outside the DevContainer works fine. There, the colleague is not asked to provide a username/password. I cannot reproduce this issue on my MacBook, there authentication works just fine inside and outside the container.

Multiple colleagues are experiencing this issue on multiple machines.

There is also not more that I can get from the logs. Even with GIT_TRACE=1 all I get at the end is just Authentication failed for .

What I've tried so far:

• If I remove the credential helper from the config, VS Code asks me for username and password. However, even after triple verifying the username/password and with/without the domain and with multiple users, we still keep getting authentication failed. Desired behaviour would be to not have remove the credential helper, but it was worth a shot.
• Putting the username in the remote URL doesn't resolve it either.

Let me know where/how I can get more useful logs explaining why it failed.

[chrmarti]

You might need to set useHttpPath for your DevOps server's URL. In the command below replace https://dev.azure.com with the URL for your DevOps server and run it in the Dev Container to try:

git config --global credential.https://dev.azure.com.useHttpPath true

Also check which credential manager is installed on the local machine. We recommend GCM these days, but maybe you have it working with a different one: https://learn.microsoft.com/en-us/azure/devops/repos/git/set-up-credential-managers?view=azure-devops

If that doesn't help please append the Dev Containers log from when this failed. (F1 > Dev Containers: Show Container Log)