Databases
StackOverflow2013
Postsdbo
POWebSVN - Authentication for paths in the repository
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWebSVN - Authentication for paths in the repository
    primarykey
    data
    text
    <p>I need simple 'to-the-point' tutorial or neat exemple of How to implement authorization for paths (checkout diretories) out of a single Subversion repository, using WebSVN.</p> <p>Lets say repository is /svn/repos/r_project Two checkout (paths) from this repos are /svn/repos/path1 and /svn/repos/path2 ... I want to protect each path (directory) with a different username/password.</p> <p>Subversion and WebSVN are installed on Unix Apache (redhat). Already i can see the two paths in the WebSVN repository front page - without any protection this is working fine. </p> <p>I know how to protect individual web index page with .htpasswd but anything i have tried to protect individual paths in the repository through WebSVN page has failed. </p> <p>Tx </p> <p>[EDIT nov26]</p> <p>Up to date situation to make it clear: Paths i have:</p> <pre><code>Home path in unix: '/var/www/' Path of WebSVN: '/var/www/websvn2' Path to repository: '/svn/repos' Created repository is '/svn/repos/r_project') // so r_project is the repository name Two checkout directories of that repository:'/svn/repos/path1' and '/svn/repos/path2' </code></pre> <p>In <strong>httpd.conf</strong> i have locations for SVN and WEBSVN (i do have the necessary modules):</p> <pre><code>&lt;Location /repos&gt; DAV svn SVNParentPath /var/www/svn/repos AuthType Basic AuthName "Subversion repository" AuthUserFile /etc/svn-auth-file Require valid-user &lt;/Location&gt; &lt;Location /websvn210/&gt; Options FollowSymLinks AuthType Basic AuthName "Subversion Repository" Require valid-user AuthUserFile /etc/svn-auth-file &lt;/Location&gt; </code></pre> <p>For now, 'svn-auth-file' contains password for one user name. Put in '/etc' directory.</p> <p>In <strong>config.php</strong> file of WebSVN i have:</p> <pre><code>$config-&gt;parentPath("/var/www/svn/repos"); $config-&gt;useAuthenticationFile('/etc/svn-auth-file'); // Global access file </code></pre> <hr> <p>I'm able to see checkout directories 'path1' and 'path2' as regular index page with files in the browser (ex: 'http://mydomain/svn/repos/path1'). However, when i go for 'http://mydomain/websvn210' in the browser i only get the login (ok) than an empty home page of WebSVN - that is, no repository or checkout paths! </p> <p>That's first problem: empty page. Second, will be to have different login for each path. Note: those paths (checkouts) are only for reading or downloading (no commit done from Subversion).</p> <p>THanks. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USvolvox
    1. USvolvox
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWebSVN - Authentication for paths in the repository
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWebSVN - Authentication for paths in the repository
      1. USjuned
      1. VTFavorite
    3. VO
      singulars
      1. POWebSVN - Authentication for paths in the repository
      1. USBarclayVision
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload