Now you can add the LDAP configuration directives to your Apache configuration. That is why in these examples the DocumentRoot to /var/lib/svn/htdocs. If you do that then Apache will not know if it should handle those himself of if he should hand it over to the Subversion module. Update: You should not point your DocumentRoot to the directory that contains all your repositories. Create a new configuration file /etc/apache2/sites-available/svn and symlink it from /etc/apache2/sites-enabled/. I chose to put my repositories under /var/lib/svn and I will use a virtual server for it. For ease of testing make sure that you can view directory indexes. Start off by creating a directory where later on you will host Subversion repositories and create a basic Apache configuration for it. First we get Active Directory working and then we look at Subversion. I am going to implement things in such a way that makes it easy to test your configuration in between. mod_authnz_ldap works just a little bit different. Here are the relevant files:Īpache2 on Debian Etch ships with mod_authnz_ldap instead of mod_auth_ldap, so if most of the online tutorials for LDAP authentication did not work for you, that's why. Make sure that the correct modules are enabled by symlinking then from /etc/apache2/mod-enabled to /etc/apache2/mods-available. Let's start off by installing a bunch of software that we need: apache2, subversion and libapache2-svn. Back to making it work because we need Subversion before we have migrated to Open-Xchange. Fortunately our management has seen the light of day after this little misadventure and in a few months we're migrating to Open-Xchange. It's API only vaguely resembles LDAP after at least three bottles of whiskey or one pan galactic gargle blaster and squinting really, really hard. After two full days of waving dead chickens at it, trying to make any sense of it's irrational behavior I would love nothing more than to pick it up and throw it off the roof of our building, BofH style, aiming it at the PHB that bought it in the first place. Microsoft Active Directory is a bit-rotten crock that should have never seen the light of day. Sensitive people may want to skip the next paragraph. Before I explain to you how I set this all up on Debian Etch I have to get something off my chest first. To make user management easier they also wanted to use Microsoft Active Directory, so I set off on a quest to make Apache talk to our Active Directory 2003 server for authentication. Last updated on The company I work for had finally realized the benefits of a decent source code versioning system so after a short evaluation they settled on Subversion.
0 kommentar(er)
