August 29, 2008 11:07pm pdt

1. sunnycoder 22,000
2. nognew 4,350
3. Joomlajohn 4,000
4. arrkerr1... 3,875
5. dklawson 3,400
6. ramazany... 2,500
6. giltjr 2,500
8. duncan_roe 2,300
9. ramrom 2,000
9. ali-bobby 2,000
9. almilyo 2,000
9. mcuk_storm 2,000
9. jkr 2,000
9. objects 2,000
9. nickg5 2,000
9. TShortland 2,000
9. tommy13v 2,000
9. KeNt_UA 2,000
9. Kdo 2,000
20. jgbustos 1,600
20. omarfarid 1,600
22. jason1178 1,500
22. agriesser 1,500
22. _Nopik_ 1,500
25. hoboslobo 1,200

1. sunnycoder 22,000
2. arrkerr1... 5,875
3. nognew 4,350
4. Joomlajohn 4,000
5. dklawson 3,400
6. kiere 2,900
7. ramazany... 2,500
7. giltjr 2,500
9. duncan_roe 2,300
10. m1tk4 2,220
11. MacAnthony 2,000
11. poisa 2,000
11. gheist 2,000
11. ati_ozgur 2,000
11. KeNt_UA 2,000
11. ali-bobby 2,000
11. tommy13v 2,000
11. almilyo 2,000
11. ramrom 2,000
11. objects 2,000
11. jkr 2,000
11. Kdo 2,000
11. mzalfres 2,000
11. sanjooz 2,000
11. TShortland 2,000
11. nickg5 2,000
11. mcuk_storm 2,000

05.07.2008 at 08:48AM PDT, ID: 23383216

	[x] Attachment Details

How do I setup Subversion security?

Asked by jojuez in Subversion, Windows 2003 Server

Tags: Subversion, Subversion, 1.4.3, Restricting users based on Repository

I need to restrict certain users to certain repositories. I am running subversion on a windows server. I have a group of developers for which I need to restrict access to certain repositories. I have found this can be accomplished by the use of the authz file. However, I cannot seem to properly configure it. Below are the examples of my config files. Whenever I try to use the authz file I get a authorization failed when I use Tortoise. If I comment out the authz in the conf file I have no issues getting in, however, then everyone has access to every repository. Start Free Trial

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:

           
           
             Passwd file:
### This file is an example password file for svnserve.
### Its format is similar to that of svnserve.conf. As shown in the 
### example below it contains one section labelled [users]. 
### The name and password for each user follow, one account per line.  
 
[users]
 
Jim = password
jake = password
johnny = password
julian = password
 
svnserve.conf:
### This file controls the configuration of the svnserve daemon, if you
 ### use it to allow access to this repository.  (If you only allow 
### access through http: and/or file: URLs, then this file is 
### irrelevant.)   
### Visit http://subversion.tigris.org/ for more information. 
  
[general]
 
### These options control access to the repository for unauthenticated 
### and authenticated users.  Valid values are "write", "read", 
### and "none".  The sample settings below are the defaults. 
anon-access = none 
auth-access = write 
### The password-db option controls the location of the password 
### database file.  Unless you specify a path starting with a /, 
### the file's location is relative to the conf directory. 
### Uncomment the line below to use the default password file. 
password-db = passwd 
### The authz-db option controls the location of the authorization 
### rules for path-based access control.  Unless you specify a path 
### starting with a /, the file's location is relative to the conf 
### directory.  If you don't specify an authz-db, no path-based access 
### control is done. 
### Uncomment the line below to use the default authorization file. 
authz-db = authz 
### This option specifies the authentication realm of the repository. 
### If two repositories have the same authentication realm, they should 
### have the same password database, and vice versa.  The default realm 
### is repository's uuid. 
# realm = My First Repository
 
AUTHZ:
### This file is an example authorization file for svnserve.
 ### Its format is identical to that of mod_authz_svn authorization
### files. 
### As shown below each section defines authorizations for the path and 
### (optional) repository specified by the section name. 
### The authorizations follow. An authorization line can refer to a 
### single user, to a group of users defined in a special [groups] 
### section, or to anyone using the '*' wildcard.  Each definition can 
### grant read ('r') access, read-write ('rw') access, or no access 
### (''). 
  
[groups] 
devel = Jim, jake 
admin = johnny 
market = julian  
 
# [/foo/bar] 
# harry = rw 
# * =
 
[repository:svn://172.16.18.19/development]
 @devel = rw 
@admin = rw 
@market =
 # * = r
 
[repository:svn://172.16.18.19/marketing]
 @devel =
@admin = rw
@market = rw

           
         

Keywords: How do I setup Subversion security?

	Title
1	apache conf
2	how to make security to svn repository
3	Restricting Citrix connections to an IP r…
4	Restricting Remote Users to Specific F…
5	Ubuntu repository
6	Need to Merge Restrictive Groups

Loading Advertisement...

20080716-EE-VQP-32 / EE_QW_2_20070628

How do I setup Subversion security?

Asked by jojuez in Subversion, Windows 2003 Server

Tags: Subversion, Subversion, 1.4.3, Restricting users based on Repository

About this solution