Versions Compared

Key

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

...

  1. If the correct credentials are stored there, it's fine.
  2. If not, Windows will ask for credentials:
  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:
  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).


http(s)-Passwort is asked again after restart

A user reported that on his Linux system with older Git 1.8.3.1 he entered https passwords and told SmartGit to store it, but after a restart he had to re-enter them. Building Git from sources and using that (here: latest version 2.27) solved this problem.

Debug logging: enable injector logging

...