[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

adding LDAP access to existing svn+ssh access

From: Ted Stern <dodecatheon_at_gmail.com>
Date: Fri, 13 Nov 2009 12:35:19 -0800

Hi all,

I have set up a subversion repository according the svn+ssh "single
account" recommendation:

     http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshtricks

I have a single account, "svnuser", on a specific host, "svnhost".

I have a script for a user to run which assists them in generating an
ssh rsa keypair. Then they convey the public key to me and I install
it in svn_at_svnhost:.ssh/authorized_keys so that svnserve is run with
the correct repository location and user name.

I also have a post-commit hook set up that will automatically update
several working copy locations when particular directories are checked
in. The svnuser account has rsa keypair ssh access into a similar
account on remote working copy hosts.

This works great for a small number of users, but now I need to scale
up to several hundred people accessing the repository, and setting up
keys for svn+ssh is too much administration.

I have a basic idea on how to get WebDAV+LDAP working, but I would
like to ensure that the post-commit hook script is run as svnuser and
not apache.

At the same time, I want to preserve the svn+ssh access setup I have
now to avoid hassles for current users.

I don't see a way to make these two access modes coexist. Is it
possible?

One thing I'm thinking of is allowing commits only via svn+ssh, and
make the WebDAV/LDAP access read-only.

Ted

-- 
 Frango ut patefaciam -- I break so that I may reveal
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2417740
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-13 21:36:12 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.