Add a dialog to enter my username and password in addition to the CLI integration

[AaronJWhite]

The old "git-credential-winstore" would bring up a user/pass dialog on the first connection to a git host it didn't have the credentials for. The user entered the credentials into the dialog that first time and then the git-credential-winstore would reuse the credentials for all connections after that.
I'm not getting a dialog for this when trying to connect using this credential helper. Can you include some type of documentation on how to store credentials with this in the readme? Or maybe a screenshot of what I should see.

[whoisj]

Thanks for the question. 😄

The model dialog presented by git-credential-winstore was a work around for the case when it did not have credentials stored. With git-credential-manager we use Git's native credential flow.

TL;DR
Enter your username and password at the command line when prompted. Your credentials will get stored securely and reused in future interactions.

I'll see about getting a "how does this thing actually work?" section added to the README.md.

Let's look at Git's native flow:

1. git.exe needs to work with a remote host over the HTTPS protocol and invokes git-remote-https.
2. git-remote-https negotiates with the host.
3. The host rejects git-remote-https due to lack of credentials.
4. git-remote-https fails with a reason code linked to credentials.
5. git.exe invokes git-credential in hopes of acquiring useful credentials.
6. git-credential scans Git's configuration to see if any helpers are registered.
7. git-credential invokes the helpers one at a time in the order listed in hopes of one having useful credentials for the + values.

Here is where Git Credential WinStore and Git Credential Manager differ

Winstore flow:

1. git-credential finds that credential.helper=winstore and invokes git-credential-winstore with the "get" option.
2. git-credential-winstore lacks credentials for the + and generates a modal dialog asking for credentials.
3. User enters credentials and git-credential-winstore stores them. Since empty credentials are valid credentials, the user will never see another prompt but could see an auth failure.

Manager flow:

1. git-credential finds that credential.helper=manager and invokes git-credential-manager with the "get" option.
2. git-credential-manager lacks credentials for the + .
3. git-credential-manager looks at configuration + to determine if these are basic credentials, VSO m-factor, or GitHub 2-factor authentication.
4. In the case of basic credentials, git-credential-manager tells git-credential the truth that it does not have any credentials for it.
5. git-credential then prompts the user at the command line for credentials.
6. The user enters credentials.
7. git-credential invokes git-credential-manager with the store option and supplies the credentials for storage.

[AaronJWhite]

Hi whoisj,

Thanks for the quick reply! Looks like I have it working in my environment now.
Also, instead of adding the user/pass through the command prompt can I just add the credentials directly to the windows credential manager? Just have to prefix the host with git:.

[whoisj]

can I just add the credentials directly to the windows credential manager? Just have to prefix the host with git:.

Yes, that'll work fine 😄

[jeremyepling]

@AaronJWhite You can add them directly, but having them automatically added via the Git command line is much easier. Is there a reason you don't like that experience? Are you running a build agent?

[AaronJWhite]

TL;DR - I'm lazy and use simple git functions. I'm not trying to remember git syntax/commands if I don't have to. With the old credential-manager I didn't have to remember anything.

Hi @jeremyepling ,
I'm not running a build agent, but I really don't have a reason to use git directly either. I use git primarily through my development tools (mainly SublimeText) and the git plugin handles all of the complexity of remembering git commands. This lets me focus on what I am developing. The nice thing about the other credential manager was that you after you installed it (by just clicking the .exe file) you could go use your dev tools and if a password was needed you get the prompt one time and it seemingly disappeared forever. I enjoy git, hell I setup my own git server for private projects, but I'm still not a power user that feels the need to remember git commands for complex features or touch git directly at all. It would be nice if there was an option to enable the prompt like the old credential store for users like me, but adding my credentials directly to the windows credential store is ok too for now.

Thanks for your help and work on this project!

[whoisj]

@AaronJWhite thanks for the feedback, we'll take it to heart. 😄

[AndrewPardoe]

1. It would have been nice to know that there was a change in the way this works. I reinstalled this package three times, restarted my shell, etc., not able to figure out why the dialog wasn't popping up.
2. Although I use Git from the command line I've always used the credential manager. It took me a minute too long to realize that "authcode:" was looking for two factor authentication. This bad UI isn't actually your fault but I'm your user and I was confused.
3. I don't know whether cutting and pasting into a git command-line login actually works. When I hit Edit->Paste in the console, nothing appears (such as stars or dots or even clear text.) So I cancel that login and do it again, this time typing my long, secure password out of my password manager. The UI definitely took--and acknowledged--cut and paste input.

In summary, it would be nice to have a step during install where I just add my credentials. That way I'd know that you silently changed the UI.

[whoisj]

We do plan to resolve this. I've just been under a pile of workload on another project.

Once I'm out from under that, I'll come back here and fix up a bunch of these open request.

I'll re-open this just to make sure it doesn't get lost.

[AndrewPardoe]

Thanks. I love the tool.