Subversion Permissions Document AuthzsvnaccessFile Example
Choose from Digitking Blog
When using the Subversion, the authentication file AuthzsvnAccessFile can control the permissions of each directory, but there are fewer documents, less Chinese documents. The method is explained below by instance.
Environment Windows 2003 Server, LAN, Domain: Domain.com.cnapache 2.0.52SUBVERSION 1.1.0TORTOIISESVN 1.1.0LanguagePack_1.1.0_zh_cn
Example: Repository is stored under D: / Repository, there are two repository: Test and Xtest Each Repostory has the same structure: Root: 01.txt 02.txt folder 1-: 11.txt 12.txt folder 2-: 21. TXT 22.TXT Different read and write permissions for catalog 1 and 2 Basic Authentication
Modify the file: Httpd.conf: #Basic authentication
Generate username and password with apache, htpasswd -c passwd username seconds no -c. The generated username and password are in Passwd: 0: $ APR1 $ VU5 ..... $ xz / csz / 2ykopnkpb88o5p01: $ i1vwmj7jtrmpmjjvult4H12: $ APR1 $ DV5 ..... VF2MTG /p0my.wcfhx7wet13:1Apr1 $TV5..... $$$$$$$$$$$$$$$$$$$$$$$$$$$
AuthzsvnaccessFile Controls read and write permissions for each directory [TEST: /] 1 = R2 = R3 = R [TEST: / 1] 1 = RW [Test: / 2] 2 = RW
On the client, you can access it with http: // server / repository / test. You can also enter the subdirectory directly: http: // server / repository / test / 1, http: // Server / repository / test / 2. The system will require certification. For example, user 1 has read and write permissions on the directory 1, can be commit, but the modification of the directory 2 cannot be commit.
SSPI certification. Press a way that users must change a password file with a password. With SSPI certification, there is no such problem. Httpd.conf file: #SSPI authentication