Context Navigation

← Previous Change
Wiki History
Next Change →

Changes between Version 2 and Version 3 of TracModWSGI

Timestamp:: 04/13/18 11:55:05 (7 years ago)
Author:: trac
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

TracModWSGI

-                      v2
+                      v3
 = Trac and mod_wsgi =
 [http://code.google.com/p/modwsgi/ mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance.
+= Trac and mod_wsgi
+[https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance.
 [[PageOutline(2-3,Overview,inline)]]
 …
 == The `trac.wsgi` script
+Trac can be run on top of mod_wsgi with the help of the following application script, which is just a Python file, though usually saved with a `.wsgi` extension.
+Trac can be run on top of mod_wsgi with the help of an application script, which is a Python file saved with a `.wsgi` extension.
+A robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin. The script should be sufficient for most installations and users not wanting more information can proceed to [#Mappingrequeststothescript configuring Apache].
+If you are using Trac with multiple projects, you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` in trac.wsgi (note that this directory should contain //only// Trac environments, no other sub-directories):
+{{{#!python
+def application(environ, start_request):
+    # Add this to config when you have multiple projects
+    environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects')
+    ..
+}}}
 === A very basic script
 In its simplest form, the script could be:
 …
 Change it according to the path you installed the Trac libs at.
-=== Recommended `trac.wsgi` script
-A somewhat robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin.
-If you are using Trac with multiple projects, you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` in the trac.wsgi in trac.wsgi: ''
-{{{#!python
-  def application(environ, start_request):
-      Add this to config when you have multiple projects
-      environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects')
-      ..
-      ..
-}}}
 == Mapping requests to the script
 After preparing your .wsgi script, add the following to your Apache configuration file, typically `httpd.conf`:
 {{{
+{{{#!apache
 WSGIScriptAlias /trac /usr/local/trac/mysite/apache/mysite.wsgi
 <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>
 }}}
 …
 If you followed the directions [TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
 {{{
+{{{#!apache
 WSGIScriptAlias /trac /usr/share/trac/cgi-bin/trac.wsgi
 <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>
 }}}
 …
 In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi. This is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash. After adding this configuration, restart Apache, and then it should work.
 To test the setup of Apache, mod_wsgi and Python itself (ie. without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
+To test the setup of Apache, mod_wsgi and Python itself (ie without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
 {{{#!python
 …
 }}}
 For more information about using the mod_wsgi specific directives, see the [http://code.google.com/p/modwsgi/wiki/ mod_wsgi's wiki] and more specifically the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac IntegrationWithTrac] page.
+For more information about using the mod_wsgi specific directives, see the [https://code.google.com/archive/p/modwsgi/wikis mod_wsgi's wiki] and more specifically the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki IntegrationWithTrac] page.
 == Configuring Authentication
 The following sections describe different methods for setting up authentication. See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
 === Using Basic Authentication ===
+The following sections describe different methods for setting up authentication. See also [http://httpd.apache.org/docs/2.4/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
+=== Using Basic Authentication
 The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program as follows:
 {{{
+{{{#!sh
 $ htpasswd -c /somewhere/trac.htpasswd admin
 New password: <type password>
 …
 After the first user, you don't need the "-c" option anymore:
 {{{
+{{{#!sh
 $ htpasswd /somewhere/trac.htpasswd john
 New password: <type password>
 …
 }}}
+  ''See the man page for `htpasswd` for full documentation.''
+See the man page for `htpasswd` for full documentation.
 After you've created the users, you can set their permissions using TracPermissions.
 Now, you need to enable authentication against the password file in the Apache configuration:
 {{{
+{{{#!apache
 <Location "/trac/login">
   AuthType Basic
 …
 If you are hosting multiple projects, you can use the same password file for all of them:
 {{{
+{{{#!apache
 <LocationMatch "/trac/[^/]+/login">
   AuthType Basic
 …
 </LocationMatch>
 }}}
+Note that neither a file nor a directory named 'login' needs to exist.[[BR]]
 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html mod_auth_basic] documentation.
 === Using Digest Authentication ===
 For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”.
+Note that neither a file nor a directory named 'login' needs to exist. See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_basic] documentation.
+=== Using Digest Authentication
+For better security, it is recommended that you either enable SSL or at least use the "digest" authentication scheme instead of "Basic".
 You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
 {{{
 # htdigest -c /somewhere/trac.htpasswd trac admin
+{{{#!sh
+$ htdigest -c /somewhere/trac.htpasswd trac admin
 }}}
 The "trac" parameter above is the "realm", and will have to be reused in the Apache configuration in the !AuthName directive:
 {{{
+{{{#!apache
 <Location "/trac/login">
+    AuthType Digest
+    AuthName "trac"
+    AuthDigestDomain /trac
+    AuthUserFile /somewhere/trac.htpasswd
+    Require valid-user
+  AuthType Digest
+  AuthName "trac"
+  AuthDigestDomain /trac
+  AuthUserFile /somewhere/trac.htpasswd
+  Require valid-user
 </Location>
 }}}
 …
 For multiple environments, you can use the same `LocationMatch` as described with the previous method.
 '''Note: `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity. '''
+'''Note''': `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity.
 Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system:
 {{{
     LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
 }}}
 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation.
+{{{#!apache
+  LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
+}}}
+See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_digest] documentation.
 === Using LDAP Authentication
 Configuration for [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2.x and OpenLDAP: slapd 2.3.19).
+Configuration for [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2+ and OpenLDAP: slapd 2.3.19).
 . You need to load the following modules in Apache httpd.conf:
+{{{
+LoadModule ldap_module modules/mod_ldap.so
+LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
+}}}
+. Your httpd.conf also needs to look something like:
+{{{
+{{{#!apache
+  LoadModule ldap_module modules/mod_ldap.so
+  LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
+}}}
+. Your httpd.conf also needs to look something like:
+{{{#!apache
 <Location /trac/>
   # (if you're using it, mod_python specific settings go here)
 …
 </Location>
 }}}
+. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory:
+Use the following as your LDAP URL:
+{{{
+    AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
+}}}
+You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plaintext in the config, you need to use an account specifically for this task:
+{{{
+    AuthLDAPBindDN ldap-auth-user@example.com
+    AuthLDAPBindPassword "password"
+}}}
+The whole section looks like:
+{{{
+. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory. Use the following as your LDAP URL:
+{{{#!apache
+  AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
+}}}
+ You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plain text in the configuration, you need to use an account specifically for this task:
+{{{#!apache
+  AuthLDAPBindDN ldap-auth-user@example.com
+  AuthLDAPBindPassword "password"
+}}}
+ The whole section looks like:
+{{{#!apache
 <Location /trac/>
   # (if you're using it, mod_python specific settings go here)
 …
   authzldapauthoritative Off
   # require valid-user
   require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
+  Require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
 </Location>
 }}}
 …
 Note 2: You can also require the user be a member of a certain LDAP group, instead of just having a valid login:
 {{{
     Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
+{{{#!apache
+  Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
 }}}
 See also:
  - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
  - [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
  - [http://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
+ - [https://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
+ - [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
+ - [https://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
 === Using SSPI Authentication
 If you are using Apache on Windows, you can use mod_auth_sspi to provide single-sign-on. Download the module from the !SourceForge [http://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the following to your !VirtualHost:
 {{{
     <Location /trac/login>
         AuthType SSPI
         AuthName "Trac Login"
         SSPIAuth On
         SSPIAuthoritative On
         SSPIDomain MyLocalDomain
         SSPIOfferBasic On
         SSPIOmitDomain Off
         SSPIBasicPreferred On
         Require valid-user
     </Location>
+{{{#!apache
+<Location /trac/login>
+  AuthType SSPI
+  AuthName "Trac Login"
+  SSPIAuth On
+  SSPIAuthoritative On
+  SSPIDomain MyLocalDomain
+  SSPIOfferBasic On
+  SSPIOmitDomain Off
+  SSPIBasicPreferred On
+  Require valid-user
+</Location>
 }}}
 …
 See also [trac:TracOnWindows/Advanced].
+=== Using Apache authentication with the Account Manager plugin's Login form ===
+To begin with, see the basic instructions for using the Account Manager plugin's [http://trac-hacks.org/wiki/AccountManagerPlugin/Modules#LoginModule Login module] and its [http://trac-hacks.org/wiki/AccountManagerPlugin/AuthStores#HttpAuthStore HttpAuthStore authentication module].
+'''Note:''' If is difficult to get !HttpAuthStore to work with WSGI when using any Account Manager version prior to acct_mgr-0.4. Upgrading is recommended.
+Here is an example (from the !HttpAuthStore link) using acct_mgr-0.4 for hosting a single project:
+{{{
+[components]
+; be sure to enable the component
+acct_mgr.http.HttpAuthStore = enabled
+[account-manager]
+; configure the plugin to use a page that is secured with http authentication
+authentication_url = /authFile
+password_store = HttpAuthStore
+}}}
+This will generally be matched with an Apache config like:
+{{{
+<Location /authFile>
+   …HTTP authentication configuration…
+   Require valid-user
+</Location>
+}}}
+Note that '''authFile''' need not exist (unless you are using Account Manager older than 0.4). See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
+=== Using CA !SiteMinder Authentication
+Setup CA !SiteMinder to protect your Trac login URL, for example `/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, for example `/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()
+    ...
+}}}
+You do not need any Apache "Location" directives.
 === Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host
 …
  - uses Apache basic authentication for Trac authentication.
 If you want your Trac to be served from e.g. !http://trac.my-proj.my-site.org, then from the folder e.g. `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
+If you want your Trac to be served from eg !http://trac.my-proj.my-site.org, then from the folder eg `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
 Create the htpasswd file:
 {{{
+{{{#!sh
 cd /home/trac-for-my-proj/the-env
 htpasswd -c htpasswd firstuser
 …
 htpasswd htpasswd seconduser
 }}}
 Keep the file above your document root for security reasons.
 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following content:
 {{{
+Create this file for example `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` on Ubuntu with the following content:
+{{{#!apache
 <Directory /home/trac-for-my-proj/the-deploy/cgi-bin/trac.wsgi>
   WSGIApplicationGroup %{GLOBAL}
 …
 }}}
 Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
+For subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
 == Troubleshooting
 …
 === Use a recent version
 Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [http://code.google.com/p/modwsgi/issues/detail?id=100 #100] and [http://code.google.com/p/modwsgi/issues/detail?id=132 #132].
 ''Note: using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks''
 If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 0.3.4 or greater. See [trac:#10675] for details.
 === Getting Trac to work nicely with SSPI and 'Require Group' ===
 If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'.
 This WSGI script 'fixes' that:
+Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [https://code.google.com/archive/p/modwsgi/issues/100 #100] and [https://code.google.com/archive/p/modwsgi/issues/132 #132].
+'''Note''': using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks
+If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 3.4 or greater. See [trac:#10675] for details.
+=== Getting Trac to work nicely with SSPI and 'Require Group'
+If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your Apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'.
+This WSGI script fixes that:
 {{{#!python
 import os
 …
 }}}
 === Trac with PostgreSQL ===
+=== Trac with PostgreSQL
 When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as the database, the server ''may'' create a lot of open database connections and thus PostgreSQL processes.
 …
 Now Trac drops the connection after serving a page and the connection count on the database will be kept low.
+//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.//
+//This is not a recommended approach though. See also the notes at the bottom of the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki mod_wsgi's IntegrationWithTrac] wiki page.//
+=== Missing Headers and Footers
+If python optimizations are enabled, then headers and footers will not be rendered. An error will be raised in Trac 1.0.11 and later when optimizations are enabled.
+In your WSGI configuration file, the `WSGIPythonOptimize` setting must be set to `0` (`1` or `2` will not work):
+{{{#!apache
+    WSGIPythonOptimize 0
+}}}
+On Ubuntu, the WSGI mod configuration is at `/etc/apache2/mods-enabled/wsgi.conf`.
+The same issue is seen with `PythonOptimize On` in [TracModPython#Pagelayoutissues ModPython].
 === Other resources
 For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [http://code.google.com/p/modwsgi/wiki/ApplicationIssues application issues] when using mod_wsgi. The wsgi page also has a [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac Integration With Trac] document.
+For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [https://code.google.com/archive/p/modwsgi/wikis/ApplicationIssues.wiki application issues] when using mod_wsgi. The wsgi page also has a [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki Integration With Trac] document.
 ----