Changes between Version 5 and Version 6 of TracModWSGI

Timestamp:

Feb 21, 2016, 9:52:25 PM (9 years ago)

Author:

trac

Comment:

--

TracModWSGI

@@ -80 +80 @@
 <Directory /usr/local/trac/mysite/apache>
     WSGIApplicationGroup %{GLOBAL}
-    Order deny,allow
-    Allow from all
+    # For Apache 2.2
+    <IfModule !mod_authz_core.c>
+        Order deny,allow
+        Allow from all
+    </IfModule>
+    # For Apache 2.4
+    <IfModule mod_authz_core.c>
+        Require all granted
+    </IfModule>
 </Directory>
 }}}
@@ -94 +101 @@
 <Directory /usr/share/trac/cgi-bin>
     WSGIApplicationGroup %{GLOBAL}
-    Order deny,allow
-    Allow from all
+    # For Apache 2.2
+    <IfModule !mod_authz_core.c>
+        Order deny,allow
+        Allow from all
+    </IfModule>
+    # For Apache 2.4
+    <IfModule mod_authz_core.c>
+        Require all granted
+    </IfModule>
 </Directory>
 }}}
@@ -278 +292 @@
 See also [trac:TracOnWindows/Advanced].
 
+=== Using CA !SiteMinder Authentication
+Setup CA !SiteMinder to protect your Trac login URL (e.g. `/trac/login`).  Also, make sure the policy is set to include the HTTP_REMOTE_USER variable.  If your site allows it, you can set this in LocalConfig.conf:
+{{{#!apache
+RemoteUserVar="WHATEVER_IT_SHOULD_BE"
+SetRemoteUser="YES"
+}}}
+The specific variable is site-dependent.  Ask your site administrator.  If your site does not allow the use of LocalConfig.conf for security reasons, have your site administrator set the policy on the server to set REMOTE_USER.
+
+Also add a !LogOffUri parameter to the agent configuration (e.g. `/trac/logout`).
+
+Then modify the trac.wsgi script generated using `trac-admin <env> deploy <dir>` to add the following lines, which extract the `HTTP_REMOTE_USER` variable and set it to `REMOTE_USER`:
+
+{{{#!python
+def application(environ, start_request): 
+    # Set authenticated username on CA SiteMinder to REMOTE_USER variable 
+    # strip() is used to remove any spaces on the end of the string
+    if 'HTTP_SM_USER' in environ: 
+        environ['REMOTE_USER'] = environ['HTTP_REMOTE_USER'].strip()
+    ...
+}}}
+
+Note:  you do not need any Apache "Location" directives.
+
 === Using Apache authentication with the Account Manager plugin's Login form ===
 
@@ -298 +335 @@
 {{{#!apache
 <Location /authFile>
-   …HTTP authentication configuration…
+   # HTTP authentication configuration
    Require valid-user
 </Location>
@@ -398 +435 @@
 //This is not a recommended approach though. See also the notes at the bottom of the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac mod_wsgi's IntegrationWithTrac] wiki page.//
 
+=== Missing Headers and Footers
+
+If python optimizations are enabled, then headers and footers will not be rendered.
+
+In your WSGI configuration file, the `WSGIPythonOptimize` setting must be set to `0` as follows (`1` or `2` will not work):
+
+{{{#!apache
+    WSGIPythonOptimize 0
+}}}
+
+On Ubuntu, the WSGI mod configuration is at `/etc/apache2/mods-enabled/wsgi.conf`.
+
+NOTE: This is the WSGI equivalent of the same issue that happens with `PythonOptimize On` in [TracModPython#Pagelayoutissues ModPython] (see [trac:#8956]).
+
 === Other resources