Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-3731

AuthzSVNAccessFile doesn't work, error 403, on Windows Server 2008

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Invalid
    • 1.6.x
    • ---
    • mod_authz_svn
    • None
    • Windows 7

    Description

      Hello,
      
      i have installed Subversion 1.6.6 with Apache 2.2.16 as Server on Windows 
      Server 2008.
      Here my issue:
      I have installed Subversion and Apache on my Server and i also created 
      an "passwd" file that contain my users, so that works all fine. I can connect 
      and when i type in my user and password i get access to Subversion. 
      But if i actived the AuthzSVNAccessFile with the authorization, than i get no 
      access to subversion!
      
      here are my http.conf content of "svn":
      <Location /svn>
        DAV svn
        SVNParentPath E:/SVN
        SVNListParentPath on
        SSLRequireSSL
        SVNIndexXSLT "/svnindex.xsl"
        AuthType Basic
        AuthName "Subversion-Projektarchive"
        AuthUserFile "E:/Program Files/Apache2.2/userverwaltung/passwd"
        Require valid-user
        AuthzSVNAccessFile "E:/Program Files/Apache2.2/userverwaltung/svnaccessfile"
      </Location>
      
      Content of my AuthzSVNAccessFile (name of the file is: svnaccessfile.conf):
      
      [groups]
      Admin = Toni, David
      user = bob, john
      
      [/]
      * = r
      @Admin = rw
      user = r
      
      Content of Apache logs:
      
      [Mon Oct 18 09:16:51 2010] [error] [client 127.0.0.1] The URI does not contain 
      the name of a repository.  [403, #190001]
      
      regards
      Attanasio
      

      Original issue reported by attanasio

      Attachments

        Activity

          People

            subversion-importer Subversion Importer
            subversion-importer Subversion Importer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: