Shanmuganathan Sivaraj

I use VisualSVN Server Manager to manage all the repositories in our subversion server. It is a fairly simple tool to create & maintain the subversion repositories. I recently moved our subversion repositories to a different server and also upgraded the VisualSVN software from version 2.5.8 to 3.0.0.

Even though the migration process is fairly simple & straight forward, the repository access permission/authentication mechanism has changed between these versions and that requires a small manual update. If the authentication mechanism is not fixed, subversion client will not connect to the server and it will fail with an error - "Access Forbidden" or "xxxx file not found under <repository>\conf folder".

Here are the steps for a simple migration -

Copy the subversion folder from old server to the new server.
Install VisualSVN Server software on the new server and make the copied folder location as the repository location.
Open the VisualSVN Server Manager
Right Click on each repository

Repository -> Properties -> Security
On the security tab, click Add & add the required users and set their permissions.
The above step will create the necessary authentication files in the repository sub-folders.

Start the VisualSVN Server & connect to it using the subversion client.

Labels: Access Control, Access List, Authentication, migration, repositories, Repository, Security, source control, Subversion, subversion client, SVN, Tortoise SVN, upgrade, version upgrade, Visual SVN Server

Shanmuganathan Sivaraj

Previous Posts

Archives

Monday, November 10, 2014

VisualSVN Upgrade to 3.0.0 - Authentication - Access Forbidden