Changes between Version 19 and Version 20 of TracNginxRecipe

Timestamp:

Sep 15, 2012, 2:04:55 PM (12 years ago)

Author:

ryu@…

Comment:

Document how to handle auth in ngynx.

TracNginxRecipe

@@ -417 +417 @@
 }}}
 
+== Handling authentication in ngynx ==
+
+If you want to handle the authentication in ngynx rather than trac, that is also possible. Since you are proxying the tracd server from ngynx, you just have to tell ngynx to forward the Authorization header to tracd, and be sure to use the same authentication scheme in both (Basic / Digest). Also, both ngynx and trac must access the same password file, or an identical copy. As a simple example, lets assume that you are using Basic authentication. Digest would be very similar.
+
+This is the ngynx configuration snippet:
+{{{
+server {
+        location / {
+                proxy_pass http://localhost:8000;  # Replace localhost:8000 with your server:port
+                auth_basic "Restricted";
+                auth_basic_user_file htpasswd;     # Will effectively be /etc/ngynx/htpasswd in Ubuntu, check your distribution
+                proxy_pass_header Authorization;   # Here you tell ngynx to forward the Authorization header to tracd
+        }
+}
+}}}
+
+And then, you can start tracd with the following command if you use multi-project setup (notice the *):
+{{{
+tracd --port=8000 --hostname=127.0.0.1 --env-parent-dir=/home/trac --basic-auth="*,/etc/nginx/htpasswd,Restricted"
+}}}
+Or the following command if you run one tracd per project:
+{{{
+tracd --port=8000 --single-env /path/to/trac/environments/project --basic-auth="project,/etc/nginx/htpasswd,Restricted"
+}}}
+You can adjust those commands to your specific needs (daemonize, etc).
+
 == Todo ==
- * Nginx Authentication Howto
  * Post the actualy config files ''somewhere''.