Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

this might be caused by having configured a Git credential.helper (probably in your global .gitconfig or in the system-wide .gitconfig). To resolve, you may set useHttpPath option, see https://git-scm.com/docs/gitcredentials.

Details on the interaction between SmartGit and Git's credential manager on Windows

If you have credential.helper=manager configured on Windows, Git will first invoke special code which tries to retrieve the password from the Windows Credential Manager.

  1. If the correct credentials are stored there, it's fine.
  2. If not, Windows will ask for credentials:
    Image Added
  3. If you will enter the correct credentials there, it's fine.
  4. If you will enter wrong credentials there, the dialog will show up again (back to step 2, this happens a couple of times).

    Up to this point SmartGit was not involved in the credentials prompt at all.

  5. If you cancel the dialog, Git will invoke the GIT_ASKPASS environment variable callback which is set by SmartGit.
  6. If the correct credentials are stored in SmartGit, they will be returned.
  7. Otherwise, SmartGit will show its own credentials dialog:
    Image Added
  8. If you will enter the correct credentials there, it's fine.
  9. If you will enter wrong credentials there, the dialog will show up again (back to step 7, this happens a couple of times).

    In either case, the credentials returned by SmartGit will be stored in the Windows Credentials Manager, too. Hence, subsequent requests for these credentials will be served directly from the Credentials Manager (step 1).

 

Debug logging: enable injector logging

...