This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Apache supports a whole raft of plug-in authentication modules.
One thing to considers, however, is "which" login you want to use. What you're actually implying is that you want to use the userid/password for that particular server machine.
I use LDAP authentication on my machines (courtesy of PAM), so there's a master database for the user logins instead of maintaining logins on a per-machine basis. It makes user administration simpler and scales well. And the users don't end up with a different password on every machine - unless I make an exception. My root accounts are not authenticated against LDAP because I don't want someone who discovers the root password to end up with the keys to the whole farm.
For LDAP authentication, I use the mod_authz module.
However, I just reread that, and subversion puts an extra spin on it. I am, in fact, using LDAP mod_authz as my subversion credentials supplier since I use the Apache server interface for both command line and for Eclipse. However, if you use the Subversion command-line client, it should prompt you once and remember thereafter if I'm not hallucinating too much. The information gets stored in the ~/.subversion directory.
If it turns out I'm mis-remembering, you should still be able to set up prompt-free access using a security certificate.
Customer surveys are for companies who didn't pay proper attention to begin with.
author & internet detective