Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-776

Apache module's Subversion support should support the SVNParentPath directive

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As of Crowd 1.2, the support for using subversion authorization files to control access on a per directory basis doesn't work if the SVNParentPath directive is used in the apache config file. This is a known limitation.

      SVNParentPath allows you to put multiple svn repositories in a directory and access them through a single URL (see http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html and http://svnbook.red-bean.com/nightly/en/svn.ref.mod_dav_svn.conf.html).

      If you do have multiple repositories you can make it work by defining apache <Location> blocks for each one and using a separate authz file for each, but it's a bit more work to set up and maintain.

      Example:

      <Location /svn/tools1>
DAV svn
SVNPath /usr/local/svnrepos/tools1
...
</Location>

<Location /svn/tools2>
DAV svn
SVNPath /usr/local/svnrepos/tools2
...
</Location>

<Location /svn/tools3>
DAV svn
SVNPath /usr/local/svnrepos/tools3
...
</Location>

            [CWD-776] Apache module's Subversion support should support the SVNParentPath directive

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3389137 ] New: JAC Suggestion Workflow 3 [ 3629565 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1393178 ] New: JAC Suggestion Workflow [ 3389137 ]
            Assignee Original: Adrian Hempel [Atlassian] [ ahempel ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 272025 ] New: Simplified Crowd Development Workflow v2 [ 1393178 ]
            jawong.adm made changes -
            Workflow Original: Feature Request Workflow [ 173750 ] New: Crowd Development Workflow v2 [ 272025 ]
            Adrian Hempel [Atlassian] made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Adrian Hempel [Atlassian] made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            shihab made changes -
            Assignee Original: David O'Flynn [Atlassian] [ doflynn ] New: Adrian Hempel [Atlassian] [ ahempel ]
            David O'Flynn [Atlassian] made changes -
            Fix Version/s New: 2.1 [ 14496 ]
            Renan Battaglin made changes -
            Description Original: As of Crowd 1.2, the support for using subversion authorization files to control access on a per directory basis doesn't work if the {{SVNParentPath}} directive is used in the apache config file. This is a known limitation.

            {{SVNParentPath}} allows you to put multiple svn repositories in a directory and access them through a single URL (see http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html and http://svnbook.red-bean.com/nightly/en/svn.ref.mod_dav_svn.conf.html).

            If you _do_ have multiple repositories you can make it work by defining apache {{<Location>}} blocks for each one and using a separate authz file for each, but it's a bit more work to set up and maintain.

            See: CWDSUP-618 for an example.
            		New: As of Crowd 1.2, the support for using subversion authorization files to control access on a per directory basis doesn't work if the {{SVNParentPath}} directive is used in the apache config file. This is a known limitation.

            {{SVNParentPath}} allows you to put multiple svn repositories in a directory and access them through a single URL (see http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html and http://svnbook.red-bean.com/nightly/en/svn.ref.mod_dav_svn.conf.html).

            If you _do_ have multiple repositories you can make it work by defining apache {{<Location>}} blocks for each one and using a separate authz file for each, but it's a bit more work to set up and maintain.

            Example:
            {noformat}
            <Location /svn/tools1>
            DAV svn
            SVNPath /usr/local/svnrepos/tools1
            ...
            </Location>

            <Location /svn/tools2>
            DAV svn
            SVNPath /usr/local/svnrepos/tools2
            ...
            </Location>

            <Location /svn/tools3>
            DAV svn
            SVNPath /usr/local/svnrepos/tools3
            ...
            </Location>
            {noformat}
            Justin Koke made changes -
            Workflow Original: jira [ 121837 ] New: Feature Request Workflow [ 173750 ]

              Unassigned Unassigned
              beb930a06022 Andrew Reid
              Votes:
              20 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: