Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Decided recently to switch VisualSVN from local users to AD users, so we could easily add other employees. I added myself, gave Read/Write privileges across the whole repo, and then tried to log in. Whether I'm using tortoisesvn or the web client, I get a 403 Forbidden error:

You don't have permission to access /svn/main/ on this server.

I Googled a bit, but only found mention of phantom groups in the authz file. I don't have any of those. Any ideas?

It works just fine with local accounts.

EDIT: Don't know why I didn't try this earlier, but adding the domain before the username makes it work, ie MAIN/Bob. This normally only works when there are conflicting local, one in AD, but for whatever reason it works here too. Kinda silly, but I can live with it.

share|improve this question

When you utilize AD for authentication the username formats are always required to be in the following format, unless you have a single domain that can auto-resolve, but even then its not good practice.

We try to train our users on using one of two formats when logging in, it makes everyones lives much easier:

  1. DOMAIN\username <- Old School NT format, old and busted
  2. username@domain.ext <- New UPN Hotness

The UPN looks like an e-mail to most people, you can even create additional UPN suffixes in AD to create custom and easy to use usernames.

share|improve this answer

Did you checked "Use Windows authentication" and "Save username in UPN format" under VisualSVN Server Properties? What does your authz-windows file looks like? You should see SSIDs of user objects there.

share|improve this answer
Use Windows authentication is checked. "Save username in UPN format" is not currently (the error persists whether it is or is not checked). authz-windows contains the SSID of my user account, and nothing else. – frustrato Dec 4 '09 at 17:38
Please paste the content of your authz-windows file here. Also, a "403 Forbidden" could also be a case-sensitive issue. – nrgyz Dec 4 '09 at 18:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.