Announcement

Collapse
No announcement yet.

svn not prompting while access svn repo

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • raje@gworks.mobi
    started a topic svn not prompting while access svn repo

    svn not prompting while access svn repo

    I have installed svn 1.9.4(apache subversion) in fedora 23 follow this link https://www.if-not-true-then-false.c...-red-hat-rhel/

    After Create and configure SVN repository, Restart the service then go to browser. http://localhost/svn/repo its not prompt to ask user name and password its goes
    directly repo files with out username and password.

    These are my Configuration :

    /etc/httpd/conf.modules.d/10-subversion.conf


    LoadModule dav_svn_module modules/mod_dav_svn.so
    LoadModule authz_svn_module modules/mod_authz_svn.so
    LoadModule dontdothat_module modules/mod_dontdothat.so

    <Location /svn>
    DAV svn
    SVNParentPath /var/www/svn

    # Limit write permission to list of valid users.
    <LimitExcept GET PROPFIND OPTIONS REPORT>
    # Require SSL connection for password protection.
    # SSLRequireSSL

    AuthType Basic
    AuthName "Subversion repositories"
    AuthUserFile /etc/svn-auth-users
    Require valid-user
    </LimitExcept>
    </Location>


    /var/www/svn/repo/conf/svnserve.conf

    [general]
    anon-access = none
    auth-access = write
    password-db = passwd
    authz-db = authz


    /var/www/svn/gworksrepo/conf/passwd


    [users]
    harry = harryssecret
    sally = sallyssecret


    Suggest me What's Wrong in my Configuration and how to fix this.





  • DougR
    replied
    Glad that it helped! Cheers.

    Leave a comment:


  • ArvedHS
    replied
    DougR, much obliged for that note about "Limit" in the Apache configuration. I had a new Subversion repository all set up, httpd all set up, htpassword accounts all set up, authz all set up, the SELinux contexts and context types etc were all good to go...and I couldn't log in from anything to save my life. Nothing was even asking for credentials. The Apache error_log unfortunately was not illuminating, precisely because it was the result of adding a <LimitExcept>. The only thing that saved me was reading your response here.

    Once I finish setting up my new home dev environment (the usual routine after getting new kit) I'll probably learn up on why the <LimitExcept> caused such a blocker. More out of curiosity than because it's important. Thanks again.

    Leave a comment:


  • DougR
    replied
    What's in your "svnserve.conf" file is immaterial when your access is going through Apache.

    So your Apache config file needs to specify more stuff. Here's an example of what I mean:

    <Location /svn>
    DAV svn
    SVNParentPath /var/www/svn
    AuthName "Subversion repositories"
    AuthType Basic
    AuthBasicProvider file
    AuthUserFile /etc/svn-auth-users
    Require valid-user
    AuthzSVNAccessFile /opt/repo/ApacheAuthZ.conf
    </Location>

    The "ApacheAuthZ.conf" file is the same format as the svnserve.conf's "authz-db" specified file but the section headers should have the repository name in them:

    [repo1]
    harry = r
    sally = rw

    [repo2]
    harry = rw
    sally = r

    See here: http://svnbook.red-bean.com/en/1.8/s...asedauthz.html

    NOTE WELL: I strongly recommend against using the "Limit" mechanisms since they are simply going to get you in trouble. They take an SVN *expert* to truly get right. I have seen their usage completely out of control without providing the appropriate restrictions, permissions, etc. For instance, there is a huge difference between the SVN 1 (https://svn.apache.org/repos/asf/sub...ebdav-protocol) and SVN 2 (https://svn.apache.org/repos/asf/sub...rotocol-v2.txt) webdav protocols and that impacts what is needed for the "Limit" mechanisms.

    Leave a comment:

Working...
X