Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SVN Commit failed, access forbidden

Recently I am facing problem of commit to SVN. The SVN server I am using is VisualSVN Server 2.5.9 and the client is TortoiseSVN 1.7.12.

At first, one user is having problem to commit files to SVN. But that user still can access to the repository and download the update. The second user on second PC is working properly. But today, the second user is having the same problem as the first user.

Commit failed

Why is this happen? How can the problem be solved? Thanks.

like image 344
user1995781 Avatar asked May 07 '13 09:05

user1995781


4 Answers

If the problem lies client side, this could be one of the causes of the error.

On clients TortoiseSVN saves client credentials under

Tortoise settings / saved data / authentication data.

I got the same error trying to commit my files, but my credentials were changed. Clearing this cache here will give you a popup on next commit attempt for re-entering your correct credentials.

like image 120
Duco L Avatar answered Oct 23 '22 02:10

Duco L


You can get the "Forbidden" error if your user account lacks access permissions to a repository or repository path; it makes sense to check authorization settings for your user account. Make sure your system administrator hasn't provided you with No Access permission to the repository path.

If you are sure that permissions are set correctly, then double-check the URL you use. URLs in Apache Subversion are case-sensitive.

Additionally, I advise you to read articles on authorization in Subversion and VisualSVN Server:

  • SVNBook about path-based authorization.
  • VisualSVN Team's article about path-based authorization. It explains the principles of SVN authorization by comparing it with Windows Access Control.
like image 43
bahrep Avatar answered Oct 23 '22 02:10

bahrep


The solution for me was to check the case sensitivity of the username. A lot of people are mentioning that the URL is case sensitive, but it seems the username is as well!

like image 4
Paul McLean Avatar answered Oct 23 '22 01:10

Paul McLean


As a new user to these two software packages, I experienced the exact same problem. As was also discovered above, my solution was to use the same case letters as is in the Repository path.

Here's a tip that I find helpful: In VisualSVN, you can right click on the path, then click "Copy URL to Clipboard" for pasting in Tortoise to be sure that the path is the identical case.

like image 2
MCone Avatar answered Oct 23 '22 01:10

MCone