I just migrated an existing svn repository to a new server. Previously the users connected using tortoise-svn over http, and when committing, would have their revision associated with there user by the svn:author property.

However now, after the move the users connect using tortoise-svn over https, and revisions no longer have associated authors.

After some research, it is my suspicion that since users are now being authenticated during the creation of the https connection, and not by subversion, that information is not being passed with their revision changes. However I have not found any way in tortoise or further down the software chain to provide this information directly.

But, I could be totally wrong. Thanks for the help.

Software stack:
Tortoise-svn v1.6.10 connecting over https to...
Apache v2.2 on Ubuntu 10.04 running ...
mod_dav_svn with ...
Subversion v1.6.12

  • This "unanswered" question was just bumped to the front page. Please click the checkmark next to your own answer to accept it and mark this question answered. – Daniel Beck May 19 '11 at 5:20

The cause of my problem was that svn users were not authenticating at all.

After the initial setup of svn/apache, I added a rule to the http.conf file allowing access to users on the local network that also applied to the svn location. Causing the svn user to no longer be prompted for authentication. I did not notice this at first, because I thought my credentials were being cached by TortoiseSVN.

I was further confused because within the svn location block I was specifying 'Require valid-user'. Which, as it turns out only requires a user to be validated if and only if a user is provided. This does not prevent access to non-users.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.