Changes between Version 1 and Version 2 of TracModWSGI
- Timestamp:
- Jun 30, 2022, 12:08:55 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracModWSGI
v1 v2 7 7 == The `trac.wsgi` script 8 8 9 Trac can be run on top of mod_wsgi with the help of an application script, which is just a Python file saved with a `.wsgi` extension.9 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. 10 10 11 11 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]. 12 12 13 If you are using Trac with multiple projects, you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` in trac.wsgi:13 If you are using Trac with multiple projects, you can specify their common parent directory in `trac.wsgi`: 14 14 {{{#!python 15 15 def application(environ, start_request): 16 # Add this to config when you have multiple projects17 environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects') 16 # Add this when you have multiple projects 17 environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects') 18 18 .. 19 19 }}} 20 20 21 Directories residing in `trac.env_parent_dir` that are not environment directories will display an error message on the [TracInterfaceCustomization#ProjectList project index page]. The directories can be excluded by listing them in a `.tracignore` file residing in `trac.env_parent_dir`. Unix [https://docs.python.org/2/library/fnmatch.html shell-style wildcard patterns] can be used in the newline separated list of directories. 22 21 23 === A very basic script 24 22 25 In its simplest form, the script could be: 23 26 … … 46 49 === A more elaborate script 47 50 48 If you are using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment. 51 If you are using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment. 49 52 50 53 To solve this problem, use the following `.wsgi` file instead: … … 56 59 import trac.web.main 57 60 def application(environ, start_response): 58 environ['trac.env_path'] = '/usr/local/trac/mysite' 61 environ['trac.env_path'] = '/usr/local/trac/mysite' 59 62 return trac.web.main.dispatch_request(environ, start_response) 60 63 }}} 61 64 62 For clarity, you should give this file a `.wsgi` extension. You should probably put the file in its own directory, since you will expose it to Apache. 65 For clarity, you should give this file a `.wsgi` extension. You should probably put the file in its own directory, since you will expose it to Apache. 63 66 64 67 If you have installed Trac and Python eggs in a path different from the standard one, you should add that path by adding the following code at the top of the wsgi script: … … 115 118 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. 116 119 117 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):120 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): 118 121 119 122 {{{#!python … … 123 126 }}} 124 127 125 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/IntegrationWithTracIntegrationWithTrac] page.128 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. 126 129 127 130 == Configuring Authentication 128 131 129 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.132 The following sections describe different methods for setting up authentication. See also [https://httpd.apache.org/docs/2.4/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide. 130 133 131 134 === Using Basic Authentication … … 147 150 }}} 148 151 149 ''See the man page for `htpasswd` for full documentation.'' 152 See the man page for `htpasswd` for full documentation. 150 153 151 154 After you've created the users, you can set their permissions using TracPermissions. … … 170 173 </LocationMatch> 171 174 }}} 172 Note that neither a file nor a directory named 'login' needs to exist.[[BR]] 173 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html mod_auth_basic] documentation.175 176 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. 174 177 175 178 === Using Digest Authentication 176 179 177 For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”.180 For better security, it is recommended that you either enable SSL or at least use the "digest" authentication scheme instead of "Basic". 178 181 179 182 You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows: … … 196 199 For multiple environments, you can use the same `LocationMatch` as described with the previous method. 197 200 198 '''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. '''201 '''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. 199 202 200 203 Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system: … … 203 206 }}} 204 207 205 See also the [http ://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation.206 207 === Using LDAP Authentication 208 209 Configuration for [http ://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2.xand OpenLDAP: slapd 2.3.19).208 See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_digest] documentation. 209 210 === Using LDAP Authentication 211 212 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). 210 213 211 214 1. You need to load the following modules in Apache httpd.conf: … … 233 236 AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)" 234 237 }}} 235 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 config, you need to use an account specifically for this task:238 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: 236 239 {{{#!apache 237 240 AuthLDAPBindDN ldap-auth-user@example.com … … 265 268 266 269 See also: 267 - [http ://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.268 - [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.269 - [http ://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.270 - [https://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap. 271 - [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. 272 - [https://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP. 270 273 271 274 === Using SSPI Authentication 272 275 273 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:276 If you are using Apache on Windows, you can use mod_auth_sspi to provide single-sign-on. Download the module from the !SourceForge [https://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the following to your !VirtualHost: 274 277 {{{#!apache 275 278 <Location /trac/login> … … 293 296 294 297 === Using CA !SiteMinder Authentication 295 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: 298 299 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`: 296 300 {{{#!apache 297 301 RemoteUserVar="WHATEVER_IT_SHOULD_BE" 298 302 SetRemoteUser="YES" 299 303 }}} 300 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. 301 302 Also add a !LogOffUri parameter to the agent configuration (e.g. `/trac/logout`). 304 305 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. 306 307 Also add a !LogOffUri parameter to the agent configuration, for example `/trac/logout`. 303 308 304 309 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`: 305 310 306 311 {{{#!python 307 def application(environ, start_request): 308 # Set authenticated username on CA SiteMinder to REMOTE_USER variable 312 def application(environ, start_request): 313 # Set authenticated username on CA SiteMinder to REMOTE_USER variable 309 314 # strip() is used to remove any spaces on the end of the string 310 if 'HTTP_SM_USER' in environ: 315 if 'HTTP_SM_USER' in environ: 311 316 environ['REMOTE_USER'] = environ['HTTP_REMOTE_USER'].strip() 312 317 ... 313 318 }}} 314 319 315 Note: you do not need any Apache "Location" directives. 316 317 === Using Apache authentication with the Account Manager plugin's Login form === 318 319 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]. 320 321 '''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. 322 323 Here is an example (from the !HttpAuthStore link) using acct_mgr-0.4 for hosting a single project: 324 {{{#!ini 325 [components] 326 ; be sure to enable the component 327 acct_mgr.http.HttpAuthStore = enabled 328 329 [account-manager] 330 ; configure the plugin to use a page that is secured with http authentication 331 authentication_url = /authFile 332 password_store = HttpAuthStore 333 }}} 334 This will generally be matched with an Apache config like: 335 {{{#!apache 336 <Location /authFile> 337 # HTTP authentication configuration 338 Require valid-user 339 </Location> 340 }}} 341 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. 320 You do not need any Apache "Location" directives. 342 321 343 322 === Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host … … 347 326 - uses Apache basic authentication for Trac authentication. 348 327 349 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:328 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: 350 329 351 330 Create the htpasswd file: … … 356 335 htpasswd htpasswd seconduser 357 336 }}} 337 358 338 Keep the file above your document root for security reasons. 359 339 360 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf`with the following content:340 Create this file for example `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` on Ubuntu with the following content: 361 341 362 342 {{{#!apache … … 381 361 }}} 382 362 383 Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.363 For subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS. 384 364 385 365 == Troubleshooting … … 387 367 === Use a recent version 388 368 389 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].390 391 '' 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''369 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]. 370 371 '''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 [https://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks 392 372 393 373 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. … … 395 375 === Getting Trac to work nicely with SSPI and 'Require Group' 396 376 397 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'.398 399 This WSGI script 'fixes'that:377 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'. 378 379 This WSGI script fixes that: 400 380 {{{#!python 401 381 import os … … 433 413 Now Trac drops the connection after serving a page and the connection count on the database will be kept low. 434 414 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.// 436 437 === Missing Headers and Footers 438 439 If python optimizations are enabled, then headers and footers will not be rendered. 440 441 In your WSGI configuration file, the `WSGIPythonOptimize` setting must be set to `0` as follows (`1` or `2` will not work): 442 443 {{{#!apache 444 WSGIPythonOptimize 0 445 }}} 446 447 On Ubuntu, the WSGI mod configuration is at `/etc/apache2/mods-enabled/wsgi.conf`. 448 449 NOTE: This is the WSGI equivalent of the same issue that happens with `PythonOptimize On` in [TracModPython#Pagelayoutissues ModPython] (see [trac:#8956]). 415 //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.// 450 416 451 417 === Other resources 452 418 453 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/IntegrationWithTracIntegration With Trac] document.419 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. 454 420 455 421 ----