##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
auth-token: expose fetched token in unified way into request attribute....
auth-token: expose fetched token in unified way into request attribute. - This will allow re-using exposed access token for HTTP views in single place - We will support also exposing tokens from url if special _auth_token will be used as url param - We'll no longer require double logic for extraction of URL/HEADER auth-tokens and have a single place to extract it.
marcink - - Load All Authors

File last commit:

r3693:f470fd2e new-ui
r4002:5f150e86 default
Show More
svn-path-permissions.rst
80 lines | 2.4 KiB | text/x-rst | RstLexer
/ docs / admin / system_admin / svn-path-permissions.rst
History | Annotation | Raw |Copy content |Copy permalink

|svn| Enabling Path Permissions

Because |RCEE| uses standard svn apache mod_svn we can take advantage of the authz configuration to protect paths and branches.

Configuring RhodeCode

  1. To configure path based permissions first we need to use a customized mod_dav_svn.conf.

    Open :file:`home/{user}/.rccontrol/{instance-id}/rhodecode.ini` file. And find svn.proxy.config_template setting. Now set a new path to read the template from. For example:

    svn.proxy.config_template = /home/ubuntu/rhodecode/custom_mod_dav_svn.conf.mako

  2. Create the file as in example: /home/ubuntu/rhodecode/custom_mod_dav_svn.conf.mako You can download one from:

    https://code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/apps/svn_support/templates/mod-dav-svn.conf.mako/

  3. Add (if not yet exists) a section AuthzSVNReposRelativeAccessFile in order to read the path auth file.

    Example modified config section enabling reading the authz file relative to repository path. Means located in /storage_dir/repo_name/conf/authz

    # snip ...

# use specific SVN conf/authz file for each repository
AuthzSVNReposRelativeAccessFile authz

Allow from all
# snip ...

    Note

    The AuthzSVNReposRelativeAccessFile should go above the Allow from all directive.

  4. Restart RhodeCode, Go to the :menuselection:`Admin --> Settings --> VCS` page, and click :guilabel:`Generate Apache Config`. This will now generate a new configuration with enabled changes to read the authz file. You can verify if changes were made by checking the generated mod_dav_svn.conf file which is included in your apache configuration.

  5. Specify new rules in the repository authz configuration. edit a file in :file:`repo_name/conf/authz`. For example, we specify that only admin is allowed to push to develop branch

    [/branches/develop]
* = r
admin = rw

    For more example see: https://svn.apache.org/repos/asf/subversion/trunk/subversion/mod_authz_svn/INSTALL/

Those rules also work for paths, so not only branches but all different paths inside the repository can be specified.
  1. Reload Apache. If all is configured correctly it should not be allowed to commit according to specified rules.