Changes between Version 26 and Version 27 of CookBook/AccountManagerPluginConfiguration


Ignore:
Timestamp:
Mar 28, 2023, 8:55:56 PM (12 months ago)
Author:
figaro
Comment:

Cosmetic updates

Legend:

Unmodified
Added
Removed
Modified
  • CookBook/AccountManagerPluginConfiguration

    v26 v27  
    1111'''General hints:'''
    1212 * Content for different section grouped in one example must be used together.
    13  * Option names are written in !CamelCase style notation, but will get (re-)written all-lowercase, if added/updated via the Trac admin web-UI. As you see, case doesn't really matter here.
    14 
    15 == Basic configuration/Kickstart
    16 
    17 !AccountManagerPlugin replaces the traditional Trac login feature with a webform, because [wiki:AccountManagerPlugin/Modules#LoginModule LoginModule] is enabled in all examples below.
     13 * Option names are written in !CamelCase style notation in this !CookBook, but will get (re-)written to lowercase under the hood once added/updated via the Trac admin web user interface.
     14
     15== Basic configuration
     16
     17The !AccountManagerPlugin replaces the traditional Trac login feature with a webform, because [wiki:AccountManagerPlugin/Modules#LoginModule LoginModule] is enabled in all examples below.
    1818
    1919=== !HtPasswdStore
     
    113113=== Create users
    114114
    115 Create the first user through browser-based registration enabled by following additional lines in `components` section of `trac.ini`:
     115Create the first user through browser-based registration enabled by following additional lines in the `components` section of `trac.ini`:
    116116{{{#!cfg
    117117[components]
     
    127127Or just use the plugins admin page form Trac's web interface, after you've given admin privileges to the first user you created.
    128128
    129 === Award an existing user account for Trac admin
     129=== Grant an existing user account for Trac admin
    130130
    131131{{{#!sh
     
    184184}}}
    185185
    186 If you made this change to an existing setup, and encounter login problems afterwards, check the cookies stored in your browser. If it holds any `trac_auth` cookies with a path other than the one defined by `auth_cookie_path`, you might have to remove those as they might conflict.
    187 
    188 Hint: Even if this setting has been introduced in Trac 0.12, it could be set in `trac.ini` for older Trac versions, and !AcctMgr will use it, specifically providing a cookie path fix-up for `trac_auth` cookies generated by Trac 0.11 and above.
     186If you made this change to an existing setup and encounter login problems afterwards, check the cookies stored in your browser. If it holds any `trac_auth` cookies with a path other than the one defined by `auth_cookie_path`, you might have to remove those as they might conflict.
     187
     188'''Note''': Even if this setting has been introduced in Trac 0.12, it could be set in `trac.ini` for older Trac versions, and !AcctMgr will use it, specifically providing a cookie path fix-up for `trac_auth` cookies generated by Trac 0.11 and above.
    189189
    190190An inherited `trac.ini` file is perfect for sharing this common setting and more between several Trac environments. Additionally delete existing `trac_auth` browser cookies. This is a one-time cleanup and only necessary to avoid unexpected login results after a cookie path changes. Of course logging out in one Trac environment will terminate the authenticated session for all participants sharing authentication as indicated by the equal cookie path setting. A mixed setup containing both authentication sharing and non-sharing environments side-by-side is valid and works well.
     
    223223==== Fixed login retry delay
    224224
    225 Fixed delay time regardless of number of successive failed login attempts
     225Fixed delay time regardless of number of successive failed login attempts.
    226226
    227227{{{#!cfg
     
    247247 * timed account locked release after a time, that depends on failed login attempt history like so:
    248248
    249 Tab. 1: lock time progression (factor 2)
     249'''Table 1''': lock time progression with factor 2:
    250250||attempt count ||delay time in seconds ^![1]^||
    251251||0 ||0
     
    265265||26 ||1 a 23 d ||
    266266||.. ||.. ||
     267
    267268^![1]^ time after previous failed login attempt
    268269
     
    280281 * timed account locked release after a time, that depends on failed login attempt history and is limited to max. 24 hours like so:
    281282
    282 Tab. 2: lock time progression (factor 5)
     283'''Table 2''': lock time progression with factor 5:
    283284||attempt count ||delay time in seconds ||
    284285||0 ||0 ||