WebFaction
Community site: login faq

I'm migrating a few subversion repositories over and wanted to host them on the same subdomain. Specifically, like this:

  • http://svn.mydomain.com/repositoryA
  • http://svn.mydomain.com/repositoryB
  • http://svn.mydomain.com/repositoryC

I created a subversion application for each repository, and linked them to a website as such:

  • /repositoryA served by repositoryA
  • /repositoryB served by repositoryB
  • /repositoryC served by repositoryC

The problem is that authentication "bleeds" from one location to the other. For example, I visit repositoryA and log in. I then visit repositoryB and have to log in again since it has different credentials. I then return to repositoryA and am asked to log in again. I assume my client (being a web browser or TortoiseSVN) is passing the Basic Authorization header from B to A and therefore causes the authorization to fail.

I found a simple workaround by using the same password on each repository. It's not ideal, so I was wondering if there was another way to do this? Thanks.

asked 10 Apr '13, 03:07

chrisch
313
accept rate: 0%


To expand on John's answer, I believe the problem is that we use "Subversion - site_name" as the HTTP authentication realm for all Subversion applications.

For example, if your site name (at https://my.webfaction.com/websites) is "svn", then the realm is "Subversion - svn" for every repository served from that site.

I think the combination of the same realm plus the same subdomain is what is causing the problem you're seeing.

I don't think HTTP authentication directives can be overridden in a .htaccess file, so I don't have an immediate solution for you, other than to change your setup to use different subdomains as John suggested.

I'll open an internal ticket for us to change the way we generate AuthName (the realm) to fix this, and I'll report back here when it is done.

permanent link

answered 11 Apr '13, 12:31

seanf
12.2k41836
accept rate: 37%

That makes sense. I'm quite certain I saw the same realm in the authentication dialog as I switched among the repositories. Either way, I was able to work around the problem by using the same password in each repository. Thanks.

(11 Apr '13, 12:41) chrisch

This issue should be resolved now - each individual SVN app will be configured with its own HTTP authentication realm.

(06 Aug '13, 19:24) seanf

HTTP basic auth works based on the domain, so you can't with HTTP basic auth.

You either have to use different domains or a different authentication method.

permanent link

answered 10 Apr '13, 17:15

johns
5.3k312
accept rate: 23%

Are you certain? I understood that Basic Authentication could be setup per directory. Also, I've seen SVN setups similar to what I described above. Is this a limitation of WebFaction or am I missing something? Thanks!

(10 Apr '13, 23:23) chrisch
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×41
×20
×3

question asked: 10 Apr '13, 03:07

question was seen: 2,469 times

last updated: 08 Aug '13, 03:38

WEBFACTION
REACH US
SUPPORT
AFFILIATE PROGRAM
LEGAL
© COPYRIGHT 2003-2019 SWARMA LIMITED - WEBFACTION IS A SERVICE OF SWARMA LIMITED
REGISTERED IN ENGLAND AND WALES 5729350 - VAT REGISTRATION NUMBER 877397162
5TH FLOOR, THE OLD VINYL FACTORY, HAYES, UB3 1HA, UNITED KINGDOM