# Changes between Version 3 and Version 4 of TracStandalone

Ignore:
Timestamp:
Mar 5, 2012 2:35:09 PM (10 years ago)
Comment:

--

### Legend:

Unmodified
 v3 Use [http://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [http://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service. === Option 3 === also cygwin's cygrunsrv.exe can be used: {{{ $cygrunsrv --install tracd --path /cygdrive/c/Python27/Scripts/tracd.exe --args '--port 8000 --env-parent-dir E:\IssueTrackers\Trac\Projects'$ net start tracd }}} == Using Authentication == 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.) 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. The general format for using authentication is: $tracd -p port --auth="base_project_dir,password_file_path,realm" project_path }}} where: * '''base_project_dir''': the base directory of the project specified as follows: * when serving multiple projects: ''relative'' to the project_path * '''realm''': the realm name (can be anything) * '''project_path''': path of the project * **--auth** in the above means use Digest authentication, replace --auth with --basic-auth if you want to use Basic auth * **--auth** in the above means use Digest authentication, replace --auth with --basic-auth if you want to use Basic auth. Although Basic authentication does not require a "realm", the command parser does, so the second comma is required, followed directly by the closing quote for an empty realm name. Examples: }}} === Using a htpasswd password file === === Basic Authorization: Using a htpasswd password file === This section describes how to use tracd with Apache .htpasswd files. Note: It is necessary (at least with Python 2.6) to install the fcrypt package in order to decode the htpasswd format. Trac source code attempt an import crypt first, but there is no such package for Python 2.6. To create a .htpasswd file use Apache's htpasswd command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache): {{{$ sudo htpasswd -c /path/to/env/.htpasswd username Then to start tracd run something like this: {{{ $tracd -p 8080 --basic-auth="projectdirname,/fullpath/environmentname/.htpasswd,realmname" /fullpath/environmentname For example: {{{$ tracd -p 8080 --basic-auth="testenv,/srv/tracenv/testenv/.htpasswd,My Test Env" /srv/tracenv/testenv }}} ''Note:'' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD). === Using a htdigest password file === === Digest authentication: Using a htdigest password file === If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read [http://httpd.apache.org/docs/2.0/programs/htdigest.html this page] from the Apache manual to get precise instructions.  You'll be prompted for a password to enter for each user that you create.  For the name of the password file, you can use whatever you like, but if you use something like users.htdigest it will remind you what the file contains. As a suggestion, put it in your /conf folder along with the [TracIni trac.ini] file. === Generating Passwords Without Apache === If you don't have Apache available, you can use this simple Python script to generate your passwords: Basic Authorization can be accomplished via this [http://www.4webhelp.net/us/password.php online HTTP Password generator].  Copy the generated password-hash line to the .htpasswd file on your system. You can use this simple Python script to generate a '''digest''' password file: {{{ }}} Note: If you use the above script you must use the --auth option to tracd, not --basic-auth, and you must set the realm in the --auth value to 'trac' (without the quotes). Example usage (assuming you saved the script as trac-digest.py): Note: If you use the above script you must set the realm in the --auth argument to '''trac'''. Example usage (assuming you saved the script as trac-digest.py): {{{ }}} Note: If you would like to use --basic-auth you need to use htpasswd tool from apache server to generate .htpasswd file. The remaining part is similar but make sure to use empty realm (i.e. coma after path). Make sure to use -m option for it.  If you do not have Apache, [trac:source:/tags/trac-0.11/contrib/htpasswd.py htpasswd.py] may help.  (Note that it requires a crypt or fcrypt module; see the source comments for details.) It is possible to use md5sum utility to generate digest-password file using such method: ==== Using md5sum It is possible to use md5sum utility to generate digest-password file: {{{ $printf "${user}:trac:\${password}" | md5sum - >>user.htdigest See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe]. === Authentication for tracd behind a proxy 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. Below is example configuration based on Apache 2.2, mod_proxy, mod_authnz_ldap. First we bring tracd into Apache's location namespace. {{{ Require ldap-group cn=somegroup, ou=Groups,dc=domain.com Require ldap-user somespecificusertoo ProxyPass http://localhost:8101/project/proxified/ # Turns out we don't really need complicated RewriteRules here at all RequestHeader set REMOTE_USER %{REMOTE_USER}s }}} 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: {{{ #!python from trac.core import * from trac.config import BoolOption from trac.web.api import IAuthenticator class MyRemoteUserAuthenticator(Component): implements(IAuthenticator) obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false', """Whether the 'Remote-User:' HTTP header is to be trusted for user logins (''since ??.??').""") def authenticate(self, req): if self.obey_remote_user_header and req.get_header('Remote-User'): return req.get_header('Remote-User') return None }}} Add this new parameter to your TracIni: {{{ ... [trac] ... obey_remote_user_header = true ... }}} Run tracd: {{{ tracd -p 8101 -r -s proxified --base-path=/project/proxified }}} === Serving a different base path than / === Tracd supports serving projects with different base urls than /. The parameter name to change this is