Changes between Version 24 and Version 25 of CookBook/AccountManagerPluginConfiguration
- Timestamp:
- May 9, 2016, 9:51:54 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CookBook/AccountManagerPluginConfiguration
v24 v25 2 2 3 3 = Cookbook: AccountManagerPlugin configuration 4 5 {{{#!box note 6 This page documents AccountManagerPlugin 0.4 and later with Trac 0.11 and later. If you are using older versions, please upgrade. 7 }}} 4 8 5 9 This page lists some useful configuration examples with hints on proper use of available options. … … 11 15 == Basic configuration/Kickstart 12 16 13 !AccountManagerPlugin replaces the traditional Trac login feature with a webform, because [wiki:AccountManagerPlugin/Modules#LoginModule LoginModule] is enabled in all examples below. No additional action is required since acct_mgr-0.4, but older plugin versions required to disable the obsoleted Trac core component explicitly: 14 {{{#!cfg 15 [components] 16 trac.web.auth.loginmodule = disabled 17 }}} 17 !AccountManagerPlugin replaces the traditional Trac login feature with a webform, because [wiki:AccountManagerPlugin/Modules#LoginModule LoginModule] is enabled in all examples below. 18 18 19 19 === !HtPasswdStore … … 23 23 password_store = HtPasswdStore 24 24 htpasswd_hash_type = md5 25 ;password_file = /var/trac/trac.htpasswd ; old style (acct_mgr < 0.4) 26 htpasswd_file = /var/trac/trac.htpasswd ; new style (acct_mgr >= 0.4) 25 htpasswd_file = /var/trac/trac.htpasswd 27 26 reset_password = false 28 27 }}} … … 48 47 * use `md5` password hash type for changed/new passwords, hint: use the cryptographically strongest, that is available on your system (and still compatible with other applications in shared-use case) 49 48 50 '''Note:''' new configuration option 'htpasswd_file' for acct_mgr-0.4 and later, see [wiki:AccountManagerPlugin/AuthStores#HtPasswdStore HtPasswdStore] module documentation for more details.51 52 49 === !HtDigestStore 53 50 … … 56 53 password_store = HtDigestStore 57 54 htdigest_realm = Trac 58 ;password_file = /var/trac/trac.htdigest ; old style (acct_mgr < 0.4) 59 htdigest_file = /var/trac/trac.htdigest ; new style (acct_mgr >= 0.4) 55 htdigest_file = /var/trac/trac.htdigest 60 56 reset_password = false 61 57 }}} … … 81 77 * set realm to select relevant htdigest file entries to '`Trac`' 82 78 83 '''Note:''' new configuration option 'htdigest_file' for acct_mgr-0.4 and later, see [wiki:AccountManagerPlugin/AuthStores#HtDigestStore HtDigestStore] module documentation for more details.84 85 79 === !SessionStore 86 80 … … 114 108 * set realm to select relevant htdigest entries to '`TracDB`' 115 109 116 '''Note:''' new configuration option 'db_htdigest_realm' for acct_mgr-0.4 and later, see [wiki:AccountManagerPlugin/AuthStores#SessionStore SessionStore] module documentation for more details.117 118 110 === Create users 119 111 … … 181 173 In a setup with multiple Trac environments per domain/host chances are that users want to work with several projects simultaneously. 40 and more environments served by a single Trac install have been reported from private networks as well as seen on the web. 182 174 183 To address the demand for authentication information sharing between some/all of the Trac environments in such a setup a login synchronization process has been introduced for acct_mgr-0.4. It relies on a non-default value for the path of `trac_auth` and `trac_auth_session` cookies. Otherwise the cookie wouldn't be recognized as related to different Trac environments by the web browser client.175 To address the demand for authentication information sharing between some/all of the Trac environments in such a setup a login synchronization process has been introduced. It relies on a non-default value for the path of `trac_auth` and `trac_auth_session` cookies. Otherwise the cookie wouldn't be recognized as related to different Trac environments by the web browser client. 184 176 185 177 In order to achieve this, set `auth_cookie_path` in the `[trac]` section of your `trac.ini` file to the '''URL''' path of your installations `TRAC_PARENT_DIR`. Assumed your projects use the URL `http://www.example.com/trac/<project_name>`, this should look like: