Can't get basic auth credentials without supplying a username about git-credential-manager

[mjcheetham]

Hello @mkincaid! Thanks for opening this issue.

You've hit the nail on head here! We're looking at an overhaul in the credential storage and recall APIs we use to match similar to how wincred does, across all platforms, to fix this issue with the basic/generic auth as well as help fix the issue of using multiple user accounts with other providers, such as the GitHub Provider (see #160).

Watch this space for a change that'll introduce these changes 😁

[mjcheetham]

Hi @mkincaid! Update for you on this one, we've got a pre-release out now which should fix this issue with basic auth and requiring a username.

https://github.com/microsoft/Git-Credential-Manager-Core/releases/tag/v2.0.246-beta

It's set as a pre-release at the moment, so isn't available on Homebrew yet, and not yet bundled with Git for Windows.

[mjcheetham]

Closing this issue now that the a release is available with this fix.
https://github.com/microsoft/Git-Credential-Manager-Core/releases/tag/v2.0.252-beta

[bbezanson]

@mjcheetham I tried installing the update for Git for Windows the other day (the 2.0.252 beta) which should have the above fix listed.

In order for my credentials to work, I needed to add allowWindowsAuth = true to the configuration file. I know you said that is fixed for a future release: #194

But I wanted to get things working now.

With the above fix, I was able to enter my user id and password and get my git command to run. However, when I ran the command again I was also prompted for my user id and password -- so for me the above defect fix does not seem to work in the 2.0.252 beta.

We are using a locally hosted bitbucket server using our corporate LDAP for authentication. I ended up reverting to the older (now deprecated) credential manager.

[mjcheetham]

@bbezanson could you please raise a new issue with this problem, including output when you set the GCM_TRACE environment variable to 1? Thanks!