This question already has an answer here:
- SVN Commit failed, access forbidden 5 answers
I am having some issue with some SVN users where they get the following message
Access to '/SVN/[repo name]/!svn/me' forbidden
I am having some issues figuring out the root cause of it.
The current setup is using Visual SVN on windows. We are using SVN security for the users, not AD. The users are that are having some issue are vendors(but not all of them), so they do have different permissions then an average user. But the weird thing is, I shadowed the user using Live meeting. They try to commit and get the message above. I clear their credentials from Tortoise SVN and use mine and everything is fine. The user is logged into the server as themselves and using my user info for SVN. But their is no link between the SVN users and windows users. Also the user was initially able to commit new files. I looked through SVN and I dont see anything wrong. Any ideas? Anyway to get more information about what is wrong.
Using OS X and svn command line, I get this error when I checkout another application from the same server with another username.
My solution is to clear the credential. The key point is to find where credential information is located. Run
svn auth
to can see the detail. In my case, it is located at/Users/joy.zhu/.subversion/auth/svn.simple
. There is cache file, just remove it.Update (Or commit...) again, username/password are asked, then you can enter the correct data. Everything goes well then.
Sorry, bahrep was correct that the url had an issue since it was case-sensitive. I am confused why when I cleared the credentials and put in my how the url was corrected.
I was able to correct the URL in TortoiseSVN, by:
Check authentication data.
In TortoiseSVN: settings\Saved Data\Authentication Data\Clear...
Perhaps you have more than one user/pass
I had encountered the similar problem(in windows os), and share my solution here.
problem:
solution:
Delete the configuration block similar to the following
run
services.msc
Restart SVN serviceFor me the reason wasn't URL case-sensitivity but http vs. https. The solution was to relocate from
to
In my case i was getting the same "Access Denied.." message and my repository URL was correct.
This worked out for me
enter image description here