Hey Erik
Sorry I mailed you directly the first time.
On 7/3/06, Erik Huelsmann <ehuels@gmail.com> wrote:
>
>
> No. Any more information on your authentication setup would be very
> usefull in determining the actual problem. A snippet of your apache
> configuration (Location block) even more.
Basically I followed the Help document from TortoiseSVN to setup the server
(TortoiseSVN Help -> Setting Up A Server -> Apache Based Server)
This is the location block for subversion in the Apache conf file:
### Subversion ###
<Location /svn>
DAV svn
SVNParentPath "E:/subversion/"
AuthType Basic
AuthName "Subversion repositories"
AuthUserFile passwd
AuthzSVNAccessFile svnaccessfile
Require valid-user
SetOutputFilter DEFLATE
SVNListParentPath on
</Location>
the svnaccessfile looks like this:
(I know it's not perfect and we're probably going to review it in the near
future)
[groups]
private = user1
admin = user1
consult = user3, user4
devteam = user1, user2
docs = user1, user3
scripts = user1, user3
# Default access rule for ALL repositories
# Everyone can read, admins can write, default users have no access by
default
[/]
* = r
@admin = rw
user3 =
user2 =
user4 =
# Give private developers complete access to their private project repos
[private:/]
@private = rw
# Give company users read-only access to the company repos, except admin who
has full access
[company:/]
@admin = rw
user3 = r
user2 = r
user4 = r
# Give default users read access to the entire testproject project
[company:/testproject]
user3 = r
user2 = r
user4 = r
# Give user2 write access to the testproject v2.1.0_test branch
[company:/projects/testproject/branches/v2.1.0_test]
user2 = rw
# Give the doc people write access to all the docs folders
[company:/testproject/docs]
@docs = rw
# Give consultants read-only and script writers full access to the scripts
folders
[company:/testproject/scripts]
@consult = r
@scripts = rw
[company:/projects/testproject/scripts]
@consult = r
@scripts = rw
[company:/projects/testproject/branches/v2.2.0/scripts]
@consult = r
@scripts = rw
# 2.2.0 branch is released. read-only access for default users
[company:/projects/testproject/branches/v2.2.0]
user3 = r
user2 = r
user4 = r
# 2.5.0 branch is released. read-only access for default users
[company:/projects/testproject/branches/v2.5.0]
user3 = r
user2 = r
user4 = r
# current branch. full access for default users
[company:/projects/testproject/branches/v3.0.0]
user3 = rw
user2 = rw
user4 = rw
We experienced the problem once with the v2.5.0 branch and today with the
v3.0.0 branch (user2 checked in code and logs showed user1 as author)
If you need more info, please let me know
Santo
Received on Mon Jul 3 14:08:31 2006