Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using Subversion 1.6.1 with Apache, on a Linux machine. The server is running over http, not https.
I want to allow people to authenticate using the same login/password that they use to log into the machine via SSH. The SVN manual only explains how to use HTTP Basic Auth and Digest authentication. But with these approaches, I need to maintain a separate list of users, and they can’t change their own passwords. I’d prefer to just use the system’s users.
The question mentions basic/digest auth. First, note that basic/digest auth refers to the protocol between server and browser to communicate the user/password (on Apache 2.2, using authentication front-end modules such as mod_auth_digest and mod_auth_basic).
Behind the scenes, Apache can use a number of different sources of user/password information to check against. mod_authn_file which uses a “password file” is a common one, and it sounds as though that’s what you’re referring to.
To access the system user/password on a Linux box, Apache project itself doesn’t provide any authentication back-end modules, but there are 3rd-party ones available. See this article which may be helpful:
Apache 2.2 authentication with mod_authnz_external