On 21 Aug 2006, at 18:58, Steve Willer wrote:
> Hey, folks.
>
>
> The problem is, we're using a local set of users in a plaintext
> file for authentication. The passwords are also not strong, because
> they're viewable by anyone who can see the file. It's pretty silly.
> We also can't use Apache2 for auth because ... well, this is
> Windows, and we have IIS all over the place, including on that one
> machine. They don't coexist very well, and taking on the whole
> Apache2 stuff as well as IIS is weird and nonstandard.
Actually, Apache and IIS coexist quite happily on the same Windows
box, we do it with our repository. When we first set up Apache, we
had some weirdness with the installer which expected port 80 to be
free, but we got around that by stopping IIS, installing Apache,
changing the port in the conf file and then restarting both Apache
and IIS.
Once we had the Apache svn config set up with authentication against
the AD domain, we didn't have to touch it ever again except for
upgrades.
>
> I have a simple solution that I'd like to get in as an enhancement.
> I think it would be quite easy to implement: allow a scriptable
> authentication host instead of a username textfile for the
> authentication. svnserve would run the program on the command line,
> giving username and password, and the auth program could return
> "yes" or "no" in its stdout (or something along those lines).
>
> If someone put this code into svn, I could contribute an AD lookup
> script. Otherwise, I'll have to set up the whole dev/build
> environment for svn, which sounds slightly daunting.
>
> As per the buddy system described in the bug tracker, I'd like to
> get some agreement before I put this in as a ticket.
>
>
> Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 21:15:45 2006