Subversion + HTTP with AD authentication, local authorization, on RHEL7

I wanted our users to be able to user their AD credentials for SVN access. I first thought about putting everything in AD, including two groups for each repo (one read, one write), but I ended up only using AD for authentication, leaving the permissions to a local file since there is only one SVN server.

That is how the apache conf file looks like:

<VirtualHost *:443>
  ServerName servername.domain

   ## Vhost docroot
  DocumentRoot "/var/www/html"

   ## Directories, there should at least be a declaration for /var/www/html

   <Location "/repos">
    Require valid-user
    Require ldap-user
    Dav svn
    AuthType Basic
    AuthName "Use your Windows Credentials"
    AuthBasicProvider file ldap
    AuthUserFile /etc/httpd/conf/auth-conf-svn
    AuthLDAPURL "ldap://DC1/dc=example,dc=domain?sAMAccountName?sub?(objectClass=*)"
    AuthLDAPBindDN "user@domain"
    AuthLDAPBindPassword "password"
    SVNParentPath /var/www/svn
    AuthzSVNAccessFile /etc/svn-acl-conf
  </Location>
</VirtualHost>

By using /var/www/svn for directory, your SELinux contexts will be correct with the default policy because of this rule:

/var/www/svn(/.*)?                                 all files          system_u:object_r:httpd_sys_rw_content_t:s0

This configuration will first check for a user in /etc/httpd/conf/auth-conf-svn, and if it can't find the specified user, it will do an ldap query on DC1.

If a valid user is found, it will check the ACL file (/etc/svn-acl-conf) to see if the user has access (read only or commit) to the repo. 

 This recipe has been tested on a RHEL7 (Red Hat Enterprise Linux 7) server, but should work on a Centos 7 server as well.

Comments

Post a Comment

Popular posts from this blog

General linux performance troubleshooting

Here's a list of commands that you should execute and then share the output to someone who can help you figure out what resource is the bottleneck in your system. Note, it requires the  sysstat  and  procps  packages (ubuntu and RHEL and its derivatives): uptime vmstat 1 10 iostat -xN 2 10 mpstat -P ALL 3 10 pidstat 1 10 free -mw (or free -m, if your OS doesn't support -w)  uptime is to see the load averages on the system. vmstat is mostly used to tell if the system is swapping or not. If you see significant numbers in the 'si' and 'so' columns, your system is most likely swapping (using the hard drive as RAM), which usually slows performance a lot. iostat is mostly used to determine if your disk subsystem is not able to cope with the load. If you see one or more lines that shows 100 or close almost constantly, it is probably the case.  If it is your swap volume, you probably saw numbers in the 'si' and 'so' columns in the  vmsta
Read more

Asterisk works under OpenVZ (no zaptel)

Hi, Just to let you know that I did a basic test with asterisk on an OpenVZ VE and it works. We only tested SIP connectivity (it would probably be complex to have Zaptel support and I don't really need it). We were able to connect to a VoIP provider using SIP ( unlimitel ) and music on hold works. The only thing I had to change to make it work is to comment out this line in /usr/sbin/safe_asterisk: #TTY=9 # TTY (if you want one) for Asterisk to run on (I guess there is no TTY9 (console # 9) on openVZ since it is a virtual machine and TTY9 is usually a physical console (monitor)). I'll soon put my asterisk server in a VE, I'll let you know how it goes. I also use Unlimitel and ATAs to link my PSTN line and cordless phones.
Read more