2

While clicking the button to generate git credentials under Azure DevOps, the option is loading with an anonymous exception, and the git credentials are not getting generated for a particular AD User.

How can I get past this error?

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
JoseMidhun
  • 31
  • 1
  • 4
  • Or generate a Personal Access Token with the Code (read & Write) permission. The git credentials with username & password are no longer the recommended way to access Azure DevOps. If you install Git Credentials Manager Core, is will do this on your behalf. Your admin can disable basic auth and personal access tokens for the organisation, in which case you're out of luck. – jessehouwing Jan 14 '22 at 08:24

2 Answers2

3

This is an known issue reported in this Azure DevOps event: https://status.dev.azure.com/_event/282616310

Our engineers are still working on this event, and they have taken some measures to improve things. You can follow this event to get the latest update for it.

When you click the "Generate Git Credentials" button, it essentially generates a PAT (Personal Access Token) with the scope "Code (Read & write)" for your account.

So, if the issue still exists on your side, as a workaround, you can try to manually create a PAT with the scope "Code (Read & write)" for your account.

Bright Ran-MSFT
  • 5,190
  • 1
  • 5
  • 12
0

The documentation specifies

The Git Credential Manager is an optional tool that makes it easy to create PATs when you're working with Azure Repos. Sign in to the web portal, generate a token, and then use the token as your password when you're connecting to Azure Repos.

PATs are generated on demand when you have the credential manager installed.
The credential manager creates the token in Azure DevOps and saves it locally for use with the Git command line or other client.

So make sure you have:

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250