| 62 | | {{{#!div |
| 63 | | Once the service is installed, it might be simpler to run the Registry Editor rather than use the `reg add` command documented above. Navigate to:[[BR]] |
| 64 | | `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tracd\Parameters` |
| 65 | | |
| 66 | | Three (string) parameters are provided: |
| 67 | | ||!AppDirectory ||C:\Python26\ || |
| 68 | | ||Application ||python.exe || |
| 69 | | ||!AppParameters ||scripts\tracd-script.py -p 8080 ... || |
| 70 | | |
| 71 | | Note that, if the !AppDirectory is set as above, the paths of the executable ''and'' of the script name and parameter values are relative to the directory. This makes updating Python a little simpler because the change can be limited, here, to a single point. |
| 72 | | (This is true for the path to the .htpasswd file, as well, despite the documentation calling out the /full/path/to/htpasswd; however, you may not wish to store that file under the Python directory.) |
| 73 | | }}} |
| 74 | | |
| 96 | | Tracd provides support for both Basic and Digest authentication. Digest is considered more secure. The examples below use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the command line. |
| 97 | | |
| 98 | | The general format for using authentication is: |
| | 75 | Using tracd with Apache .htpasswd files: |
| | 76 | |
| | 77 | To create a .htpasswd file using htpasswd: |
| | 78 | |
| | 79 | {{{ |
| | 80 | $ htpasswd -c /path/to/env/.htpasswd username |
| | 81 | }}} |
| | 82 | then for additional users: |
| | 83 | {{{ |
| | 84 | $ htpasswd /path/to/env/.htpasswd username2 |
| | 85 | }}} |
| | 86 | then for starting the tracd (on windows skip the "=" after --basic-auth): |
| | 87 | {{{ |
| | 88 | tracd -p 8080 --basic-auth=environmentname,/fullpath/environmentname/.htpasswd,/fullpath/environmentname /fullpath/environmentname |
| | 89 | }}} |
| | 90 | |
| | 91 | `environmentname` is the directory name of the Trac project folder, as opposed to `/fullpath/environmentname` which is the full path to the Trac project folder. See below for another example. |
| | 92 | |
| | 93 | Tracd provides support for both Basic and Digest authentication. The default is to use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the examples below. (You must still specify a dialogic "realm", which can be an empty string by trailing the BASICAUTH with a comma.) |
| | 94 | |
| | 95 | ''Support for Basic authentication was added in version 0.9.'' |
| | 96 | |
| | 97 | The general format for using authentication is (replace `--auth` with `--basic-auth` if you want to use Basic auth): |
| | 98 | |
| 219 | | |
| 220 | | == Reference == |
| 221 | | |
| 222 | | Here's the online help, as a reminder (`tracd --help`): |
| 223 | | {{{ |
| 224 | | Usage: tracd [options] [projenv] ... |
| 225 | | |
| 226 | | Options: |
| 227 | | --version show program's version number and exit |
| 228 | | -h, --help show this help message and exit |
| 229 | | -a DIGESTAUTH, --auth=DIGESTAUTH |
| 230 | | [projectdir],[htdigest_file],[realm] |
| 231 | | --basic-auth=BASICAUTH |
| 232 | | [projectdir],[htpasswd_file],[realm] |
| 233 | | -p PORT, --port=PORT the port number to bind to |
| 234 | | -b HOSTNAME, --hostname=HOSTNAME |
| 235 | | the host name or IP address to bind to |
| 236 | | --protocol=PROTOCOL http|scgi|ajp |
| 237 | | -q, --unquote unquote PATH_INFO (may be needed when using ajp) |
| 238 | | --http10 use HTTP/1.0 protocol version (default) |
| 239 | | --http11 use HTTP/1.1 protocol version instead of HTTP/1.0 |
| 240 | | -e PARENTDIR, --env-parent-dir=PARENTDIR |
| 241 | | parent directory of the project environments |
| 242 | | --base-path=BASE_PATH |
| 243 | | the initial portion of the request URL's "path" |
| 244 | | -r, --auto-reload restart automatically when sources are modified |
| 245 | | -s, --single-env only serve a single project without the project list |
| 246 | | }}} |
| 265 | | === Using tracd behind a proxy |
| 266 | | |
| 267 | | In some situations when you choose to use tracd behind Apache or another web server. |
| 268 | | |
| 269 | | In this situation, you might experience issues with redirects, like being redirected to URLs with the wrong host or protocol. In this case (and only in this case), setting the `[trac] use_base_url_for_redirect` to `true` can help, as this will force Trac to use the value of `[trac] base_url` for doing the redirects. |
| 270 | | |
| 271 | | If you're using the AJP protocol to connect with `tracd` (which is possible if you have flup installed), then you might experience problems with double quoting. Consider adding the `--unquote` parameter. |
| 272 | | |
| 273 | | See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe]. |
| 274 | | |
| 275 | | === Authentication for tracd behind a proxy |
| 276 | | It is convenient to provide central external authentication to your tracd instances, instead of using {{{--basic-auth}}}. There is some discussion about this in #9206. |
| 277 | | |
| 278 | | Below is example configuration based on Apache 2.2, mod_proxy, mod_authnz_ldap. |
| 279 | | |
| 280 | | First we bring tracd into Apache's location namespace. |
| 281 | | |
| 282 | | {{{ |
| 283 | | <Location /project/proxified> |
| 284 | | Require ldap-group cn=somegroup, ou=Groups,dc=domain.com |
| 285 | | Require ldap-user somespecificusertoo |
| 286 | | ProxyPass http://localhost:8101/project/proxified/ |
| 287 | | # Turns out we don't really need complicated RewriteRules here at all |
| 288 | | RequestHeader set REMOTE_USER %{REMOTE_USER}s |
| 289 | | </Location> |
| 290 | | }}} |
| 291 | | |
| 292 | | Then we need a single file plugin to recognize HTTP_REMOTE_USER header as valid authentication source. HTTP headers like '''HTTP_FOO_BAR''' will get converted to '''Foo-Bar''' during processing. Name it something like '''remote-user-auth.py''' and drop it into '''proxified/plugins''' directory: |
| 293 | | {{{ |
| 294 | | #!python |
| 295 | | from trac.core import * |
| 296 | | from trac.config import BoolOption |
| 297 | | from trac.web.api import IAuthenticator |
| 298 | | |
| 299 | | class MyRemoteUserAuthenticator(Component): |
| 300 | | |
| 301 | | implements(IAuthenticator) |
| 302 | | |
| 303 | | obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false', |
| 304 | | """Whether the 'Remote-User:' HTTP header is to be trusted for user logins |
| 305 | | (''since ??.??').""") |
| 306 | | |
| 307 | | def authenticate(self, req): |
| 308 | | if self.obey_remote_user_header and req.get_header('Remote-User'): |
| 309 | | return req.get_header('Remote-User') |
| 310 | | return None |
| 311 | | |
| 312 | | }}} |
| 313 | | |
| 314 | | Add this new parameter to your TracIni: |
| 315 | | {{{ |
| 316 | | ... |
| 317 | | [trac] |
| 318 | | ... |
| 319 | | obey_remote_user_header = true |
| 320 | | ... |
| 321 | | }}} |
| 322 | | |
| 323 | | Run tracd: |
| 324 | | {{{ |
| 325 | | tracd -p 8101 -r -s proxified --base-path=/project/proxified |
| 326 | | }}} |
| | 237 | === Using apache rewrite rules === |
| | 238 | In some situations when you choose to use tracd behind apache, you might experience issues with redirects, like being redirected to URLs with the wrong host or protocol. In this case (and only in this case), setting the `[trac] use_base_url_for_redirect` to `true` can help, as this will force Trac to use the value of `[trac] base_url` for doing the redirects. |
