Configuring GIT on a server in a Windows / Active Directory environment

Question

We are considering setting up GIT for use by Windows clients in an Active Directory environment, and I wonder what configurations people have had successfully.

First we installed HTTPS / Apache with basic authentication against AD. However, this requires that credentials be provided for each click from the client. Would Kerberos Be Less Painful?

I doubt the use of SSH pairs and private keys as this will increase the service required by our IT team. Is it possible to associate the private key with the AD account so that it can be automatically downloaded using GIT (some kind of replacement for PLink.exe related to AD)?

I mainly try to minimize the ongoing pain for both the IT team and the developers. Am I wasting my time? Should I look for Mercurial instead?

To clarify: I have experience with GIT on Windows with github as remote, and I like it. However, I am happy to take a look at Mercurial (which I used, but only a little), if that means better support for Windows authentication.

Answer 1

? ?
, Kerberos LDAP AD, / (, ), () , HTTP SSH. Kerberos , , HTTP msysgit SPNEGO SSPI GSSAPI.

, Mercurial , . .