Authentication failed issue - Azure DevOps

[RoHeck]

The problem

I have the same probleme like in this issue #18586
I was asked to create a new issue with my log files.

I use Windows 11 with Github-Desktop 3.3.17 (everything worked with 3.3.14)
My repro is hosted with Azure DevOps

Release version

3.3.17

Operating system

Windows 11

Steps to reproduce the behavior

No response

Log files

2024-05-10.desktop.production - issue.log

Screenshots

Additional context

No response

[sergiou87]

Hey @RoHeck 👋

Thank you for your report and your logs. Is it possible that you're providing the wrong password when asked for credentials?

More specifically, Azure DevOps repos require "Personal Access Tokens" (instead of your account password) which can be generated following the instructions in this article: https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows

Please, let us know if that helps.

[RoHeck]

In the past I was able to connect without a personal access token, but i have tried it out with a token just now, but it results with the same issue.

[erencylk]

I have same problem. I was able to access via PAT, but now we are getting the same error.

[steveward]

@RoHeck just to confirm so we're not missing anything -- did you ensure your access token had the correct scopes set? One way to check would be to use the same token on the command line to clone a repo.

I have same problem. I was able to access via PAT, but now we are getting the same error.

@erencylk are you also using Azure DevOps? Can you share the log file from GitHub Desktop from a day you encountered this error?

[erencylk]

@RoHeckhiçbir şeyi kaçırmamamızı sağlamak için sadece onaylamak amacıyla -- erişim belirtecinizin doğru kapsamların ayarlandığından emin oldunuz mu? Kontrol etmenin bir yolu, bir repoyu klonlamak için komut satırında aynı belirteci kullanmak olacaktır.

Bende de aynı sorun var. PAT üzerinden erişebildim ancak şimdi aynı hatayı alıyoruz.

@erencylksiz de Azure DevOps kullanıyor musunuz? Bu hatayla karşılaştığınız günün günlük dosyasını GitHub Desktop'tan paylaşabilir misiniz?

I'm using Azure DevOps server. Git desktop version 3.3.14 works but when I update it it doesn't work

[RoHeck]

I have tried it with a read/write, as well as with a full-access token.

Is there a way to download 3.3.14 just that i can use a functional version for the moment?

[jonaspetraska7]

Go to your install path : %LOCALAPPDATA%/GitHubDesktop/app-3.3.14 there should be a GitHubDesktop.exe for the 3.3.14 version, make a shortcut and use 👍

[RoHeck]

@jonaspetraska7 Perfect! It works - thank you very much!

[sergiou87]

@erencylk Could you upload the log file from GitHub Desktop so that I could get some more information about this error? To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs.
The log files are created daily -- please upload a log file as an attachment from a day where you experienced the issue.

@RoHeck just curious, does your repo use submodules or LFS? 🤔 Does it work if you run git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin from the terminal (which is exactly what GitHub Desktop does) ? It should ask you for credentials too.

[ianfife]

Getting the same issue.

[RoHeck]

git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin
dosen't work too
but a simple "git fetch" as well as "git fetch --progress --prune --recurse-submodules=on-demand origin" works

[sergiou87]

Hello 👋

Please, try the latest beta (3.3.19-beta2) from https://desktop.github.com/beta which includes support for multiple git credentials on the same host based on different repository paths and let us know if it works.

After updating, you might need to re-enter your credentials for your Azure DevOps repositories.

For hosts other than dev.azure.com, you might need to set useHttpPath to true for whatever domain your repos are hosted on. For example, for gitlab:

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

Thank you for your patience 🙏