Scenario: Windows server in a AD domain hosting a Subversion repository using SVNSERVE only (no Apache), and not VisualSVN.
Objective: Authenticate users to the Subversion repository via SASL through GSSAPI to a Windows domain via Kerberos.
Frequent postings in multiple sites indicate users often dead-end in this configuration with a “Could not obtain list of SASL mechanisms.” I’ve not seen any instance where this is actually running. Does anyone have this running?
I ask this question as a result of a 2011 posting in a Gentoo forum in which someone in precisely this scenario reviewed the relevant source tarballs and concluded that while, at one time, such a configuration probably worked, the files necessary for it are no longer in the source.
Now, I don’t assert that claim to be accurate, but I do know I am stuck at precisely the same point, and I’ve not yet seen any posts that claim “victory” over such a setup. If you have, please advise details!
Many thanks in advance.
After earning a “tumbleweed” badge for this unanswered question, and considerable additional research on my own, I’ve come to the conclusion that the subject combination for Subversion under Windows is, in fact, not possible under the current code base. I believe something in the SASL authentication layer is the problem here, with some source removed or significantly changed to “break” what did, I believe, work at one point.
My solution has been to add Apache to the mix with mod_auth_sspi, and while it does slow down the repository some, the authentication works perfectly. This appears to be the “fix” for the authentication requirement.