-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git complains about bad input using credential.credentialType set to oauth #327
Comments
Hi @davehcdn, thanks for the interest in GCM Core's new "PAT-less" mode for Azure Repos. The setting to control this experimental option was renamed at some point during development, but the PR description linked still shows the old setting. To enable PAT-less mode now, you need to run: git config --global credential.azreposCredentialType oauth |
I've updated the release notes to point to this document that explains in more detail the different "credential/auth modes" for Azure Repos, and links to the new setting names. |
@mjcheetham I tried it out and it seems to work but there are two things:
|
The Please can you run this again with both the
I've just updated this; thanks! |
Bounced to browser to do the Auth Here is the gcm.log output
|
@mjcheetham does that output help at all? Coworkers tested on windows 10 and they didn't get the echo back |
It looks like the [credential]
helper =
helper = /usr/local/share/gcm-core/git-credential-manager-core
azreposCredentialType = oauth |
Thank you @mjcheetham - the issue is now resolved. I foolishly thought I knew better and I had removed that empty line from my git config at some point. I have added it back and it no longer echos out the bad input. |
Installed 2.0.394-beta+3fc6791abf on my mac using homebrew
I can successfully do a git clone (GCMCore opens a browser window for my MFA / Authentication) however when I look in https://dev.azure.com/{removed}/_userSettings/tokens I can see that it generated a new PAT still...
I thought this should be all the configuration which I need to prevent using a PAT, reading the notes from #294
The text was updated successfully, but these errors were encountered: