Changes between Version 2 and Version 3 of TracFineGrainedPermissions


Ignore:
Timestamp:
08/08/15 13:07:49 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracFineGrainedPermissions

    v2 v3  
     1= Fine grained permissions = 
    12[[PageOutline(2-5, Contents, floated)]] 
    2 = Fine grained permissions = 
    3  
    4 Before Trac 0.11, it was only possible to define fine-grained permissions checks on the repository browser sub-system. 
    5  
    6 Since 0.11, there's a general mechanism in place that allows custom **permission policy plugins** to grant or deny any action on any kind of Trac resources, even at the level of specific versions of such resources. 
    7  
    8 Note that for Trac 0.12, `authz_policy` has been integrated as an optional module (in `tracopt.perm.authz_policy.*`), so it's installed by default and can simply be activated via the //Plugins// panel in the Trac administration module. 
    9  
     3[[TracGuideToc]] 
     4 
     5There is a general mechanism in place that allows custom **permission policy plugins** to grant or deny any action on any kind of Trac resource, even at the level of specific versions of such resources. 
     6 
     7That mechanism is `authz_policy`, which is an optional module in `tracopt.perm.authz_policy.*`, so it is installed by default. It can be activated via the //Plugins// panel in the Trac administration module. 
    108 
    119== Permission Policies == 
    1210 
    13 A great diversity of permission policies can be implemented, and Trac comes with a few examples.  
     11A great diversity of permission policies can be implemented and Trac comes with a few examples.  
    1412 
    1513Which policies are currently active is determined by a configuration setting in TracIni: 
    16 e.g. 
    17 {{{ 
     14 
     15{{{#!ini 
    1816[trac] 
    1917permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy 
     
    2119This lists the [#AuthzSourcePolicy] described below as the first policy, followed by the !DefaultPermissionPolicy which checks for the traditional coarse grained style permissions described in TracPermissions, and the !LegacyAttachmentPolicy which knows how to use the coarse grained permissions for checking the permissions available on attachments. 
    2220 
    23 Among the possible optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See 
    24 [trac:source:branches/0.12-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.  
     21Among the optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See 
     22[trac:source:branches/1.0-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.  
    2523 
    2624Another popular permission policy [#AuthzSourcePolicy], re-implements the pre-0.12 support for checking fine-grained permissions limited to Subversion repositories in terms of the new system. 
    2725 
    28 See also [trac:source:branches/0.12-stable/sample-plugins/permissions sample-plugins/permissions] for more examples. 
    29  
     26See also [trac:source:branches/1.0-stable/sample-plugins/permissions sample-plugins/permissions] for more examples. 
    3027 
    3128=== !AuthzPolicy ===  
    3229==== Configuration ==== 
    33 * Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (still needed for 0.12). 
    34 * Copy authz_policy.py into your plugins directory (only for Trac 0.11). 
     30* Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj]. 
    3531* Put a [http://swapoff.org/files/authzpolicy.conf authzpolicy.conf] file somewhere, preferably on a secured location on the server, not readable for others than the webuser. If the  file contains non-ASCII characters, the UTF-8 encoding should be used. 
    3632* Update your `trac.ini`: 
    37   1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section 
    38 {{{ 
     33  1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section: 
     34{{{#!ini 
    3935[trac] 
    4036... 
    4137permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy 
    4238}}} 
    43   1. add a new `[authz_policy]` section 
    44 {{{ 
     39  1. add a new `[authz_policy]` section: 
     40{{{#!ini 
    4541[authz_policy] 
    4642authz_file = /some/trac/env/conf/authzpolicy.conf 
    4743}}} 
    48   1. enable the plugin through [/admin/general/plugin WebAdmin] or by editing the `[components]` section 
    49 {{{ 
     44  1. enable the plugin through [/admin/general/plugin WebAdmin] or by editing the `[components]` section: 
     45{{{#!ini 
    5046[components] 
    51 ... 
    52 # Trac 0.12 
    5347tracopt.perm.authz_policy.* = enabled 
    54 # for Trac 0.11 use this 
    55 #authz_policy.* = enabled  
    56 }}} 
    57  
     48}}} 
    5849 
    5950==== Usage Notes ==== 
    60 Note that the order in which permission policies are specified is quite critical,  
    61 as policies will be examined in the sequence provided. 
     51 
     52Note the order in which permission policies are specified: policies are implemented in the sequence provided and therefore may override earlier policy specifications. 
    6253 
    6354A policy will return either `True`, `False` or `None` for a given permission check. `True` is returned if the policy explicitly grants the permission. `False` is returned if the policy explicitly denies the permission. `None` is returned if the policy is unable to either grant or deny the permission. 
    6455 
    65 NOTE: Only if the return value is `None` will the ''next'' permission policy be consulted. 
    66 If none of the policies explicitly grants the permission, the final result will be `False`  
    67 (i.e. permission denied). 
     56NOTE: Only if the return value is `None` will the ''next'' permission policy be consulted. If none of the policies explicitly grants the permission, the final result will be `False`, i.e. permission denied. 
    6857 
    6958The `authzpolicy.conf` file is a `.ini` style configuration file: 
    70 {{{ 
     59{{{#!ini 
    7160[wiki:PrivatePage@*] 
    7261john = WIKI_VIEW, !WIKI_MODIFY 
     
    7463* = 
    7564}}} 
    76 * Each section of the config is a glob pattern used to match against a Trac resource 
    77   descriptor. These descriptors are in the form: 
     65* Each section of the config is a glob pattern used to match against a Trac resource descriptor. These descriptors are in the form: 
    7866{{{ 
    7967<realm>:<id>@<version>[/<realm>:<id>@<version> ...] 
    8068}}} 
    81   Resources are ordered left to right, from parent to child. If any 
    82   component is inapplicable, `*` is substituted. If the version pattern is 
    83   not specified explicitely, all versions (`@*`) is added implicitly 
    84  
    85   Example: Match the WikiStart page 
    86 {{{ 
     69 
     70Resources are ordered left to right, from parent to child. If any component is inapplicable, `*` is substituted. If the version pattern is not specified explicitly, all versions (`@*`) is added implicitly. Example: Match the WikiStart page: 
     71{{{#!ini 
    8772[wiki:*] 
    8873[wiki:WikiStart*] 
     
    9176}}} 
    9277 
    93   Example: Match the attachment `wiki:WikiStart@117/attachment/FOO.JPG@*` 
    94   on WikiStart 
    95 {{{ 
     78Example: Match the attachment `wiki:WikiStart@117/attachment:FOO.JPG@*` on WikiStart: 
     79{{{#!ini 
    9680[wiki:*] 
    9781[wiki:WikiStart*] 
    9882[wiki:WikiStart@*] 
    99 [wiki:WikiStart@*/attachment/*] 
    100 [wiki:WikiStart@117/attachment/FOO.JPG] 
    101 }}} 
    102  
    103 * Sections are checked against the current Trac resource descriptor '''IN ORDER''' of 
    104   appearance in the configuration file. '''ORDER IS CRITICAL'''. 
    105  
    106 * Once a section matches, the current username is matched against the keys  
    107   (usernames) of the section, '''IN ORDER'''.  
     83[wiki:WikiStart@*/attachment:*] 
     84[wiki:WikiStart@117/attachment:FOO.JPG] 
     85}}} 
     86 
     87* Sections are checked against the current Trac resource descriptor '''IN ORDER''' of appearance in the configuration file. '''ORDER IS CRITICAL'''. 
     88 
     89* Once a section matches, the current username is matched against the keys (usernames) of the section, '''IN ORDER'''.  
    10890  * If a key (username) is prefixed with a `@`, it is treated as a group.  
    109   * If a value (permission) is prefixed with a `!`, the permission is 
    110     denied rather than granted. 
    111  
    112   The username will match any of 'anonymous', 'authenticated', <username> or '*', using normal Trac permission rules. || '''Note:''' Other groups which are created by user (e.g. by 'adding subjects to groups' on web interface page //Admin / Permissions//) cannot be used. See [trac:ticket:5648 #5648] for details about this missing feature || 
     91  * If a value (permission) is prefixed with a `!`, the permission is denied rather than granted. 
     92 
     93The username will match any of 'anonymous', 'authenticated', <username> or '*', using normal Trac permission rules. || '''Note:''' Other groups which are created by user (e.g. by 'adding subjects to groups' on web interface page //Admin / Permissions//) cannot be used. See [trac:ticket:5648 #5648] for details about this missing feature. || 
    11394 
    11495For example, if the `authz_file` contains: 
    115 {{{ 
     96{{{#!ini 
    11697[wiki:WikiStart@*] 
    11798* = WIKI_VIEW 
     
    129110 
    130111Then:  
    131   * All versions of WikiStart will be viewable by everybody (including anonymous) 
     112  * All versions of WikiStart will be viewable by everybody, including anonymous 
    132113  * !PrivatePage will be viewable only by john 
    133114  * other pages will be viewable only by john and jack 
    134115 
    135116Groups: 
    136 {{{ 
     117{{{#!ini 
    137118[groups] 
    138119admins = john, jack 
     
    155136 
    156137Some repository examples (Browse Source specific): 
    157 {{{ 
     138{{{#!ini 
    158139# A single repository: 
    159140[repository:test_repo@*] 
    160141john = BROWSER_VIEW, FILE_VIEW 
    161142# John has BROWSER_VIEW and FILE_VIEW for the entire test_repo 
     143 
     144# The default repository (requires Trac 1.0.2 or later): 
     145[repository:@*] 
     146john = BROWSER_VIEW, FILE_VIEW 
     147# John has BROWSER_VIEW and FILE_VIEW for the entire default repository 
    162148 
    163149# All repositories: 
    164150[repository:*@*] 
    165151jack = BROWSER_VIEW, FILE_VIEW 
    166 # John has BROWSER_VIEW and FILE_VIEW for all repositories 
    167 }}} 
    168  
    169 Very fine grain repository access: 
    170 {{{ 
     152# Jack has BROWSER_VIEW and FILE_VIEW for all repositories 
     153}}} 
     154 
     155Very granular repository access: 
     156{{{#!ini 
    171157# John has BROWSER_VIEW and FILE_VIEW access to trunk/src/some/location/ only 
    172158[repository:test_repo@*/source:trunk/src/some/location/*@*] 
    173159john = BROWSER_VIEW, FILE_VIEW 
    174160 
    175  
    176161# John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of all files at trunk/src/some/location only 
    177162[repository:test_repo@*/source:trunk/src/some/location/*@1] 
    178163john = BROWSER_VIEW, FILE_VIEW 
    179164 
    180  
    181165# John has BROWSER_VIEW and FILE_VIEW access to all revisions of 'somefile' at trunk/src/some/location only  
    182166[repository:test_repo@*/source:trunk/src/some/location/somefile@*] 
    183167john = BROWSER_VIEW, FILE_VIEW 
    184168 
    185  
    186169# John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of 'somefile' at trunk/src/some/location only 
    187170[repository:test_repo@*/source:trunk/src/some/location/somefile@1] 
     
    191174Note: In order for Timeline to work/visible for John, we must add CHANGESET_VIEW to the above permission list. 
    192175 
    193  
    194176==== Missing Features ==== 
    195 Although possible with the !DefaultPermissionPolicy handling (see Admin panel), fine-grained permissions still miss those grouping features (see [trac:ticket:9573 #9573], [trac:ticket:5648 #5648]). Patches are partially available, see forgotten authz_policy.2.patch  part of [trac:ticket:6680 #6680]). 
     177Although possible with the !DefaultPermissionPolicy handling (see Admin panel), fine-grained permissions still miss those grouping features (see [trac:ticket:9573 #9573], [trac:ticket:5648 #5648]). Patches are partially available, see authz_policy.2.patch, part of [trac:ticket:6680 #6680]. 
    196178 
    197179You cannot do the following: 
    198 {{{ 
     180{{{#!ini 
    199181[groups] 
    200182team1 = a, b, c 
     
    204186}}} 
    205187 
    206 Permission groups are not supported either. You cannot do the following: 
    207 {{{ 
     188Permission groups are not supported either, so you cannot do the following: 
     189{{{#!ini 
    208190[groups] 
    209191permission_level_1 = WIKI_VIEW, TICKET_VIEW 
     
    217199=== !AuthzSourcePolicy  (mod_authz_svn-like permission policy) === #AuthzSourcePolicy 
    218200 
    219 At the time of this writing, the old fine grained permissions system from Trac 0.11 and before used for restricting access to the repository has  been converted to a permission policy component, but from the user point of view, this makes little if no difference. 
    220  
    221 That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn.  
    222 More information about this file format and about its usage in Subversion is available in the  [http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html Path-Based Authorization] section in the Server Configuration chapter of the svn book. 
     201At the time of this writing, the old granular permissions system from Trac 0.11 and before used for restricting access to the repository has been converted to a permission policy component. But from the user's point of view, this makes little if any difference. 
     202 
     203That kind of granular permission control needs a definition file, which is the one used by Subversion's mod_authz_svn.  
     204More information about this file format and about its usage in Subversion is available in the [http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html Path-Based Authorization] section in the Server Configuration chapter of the svn book. 
    223205 
    224206Example: 
    225 {{{ 
     207{{{#!ini 
    226208[/] 
    227209* = r 
     
    241223==== Trac Configuration ==== 
    242224 
    243 To activate fine grained permissions you __must__ specify the {{{authz_file}}} option in the {{{[trac]}}} section of trac.ini. If this option is set to null or not specified the permissions will not be used. 
    244  
    245 {{{ 
     225To activate granular permissions you __must__ specify the {{{authz_file}}} option in the {{{[trac]}}} section of trac.ini. If this option is set to null or not specified, the permissions will not be used. 
     226 
     227{{{#!ini 
    246228[trac] 
    247229authz_file = /path/to/svnaccessfile 
    248230}}} 
    249231 
    250 If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add  
    251  
    252 {{{ 
     232If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add: 
     233 
     234{{{#!ini 
    253235authz_module_name = modulename 
    254236}}} 
    255237 
    256 where ''modulename'' refers to the same repository indicated by the `repository_dir` entry in the `[trac]` section. As an example, if the `repository_dir` entry in the `[trac]` section is {{{/srv/active/svn/blahblah}}}, that would yield the following: 
    257  
    258 {{{  
     238where ''modulename'' refers to the same repository indicated by the `repository_dir` entry in the `[trac]` section. As an example, if the `repository_dir` entry in the `[trac]` section is {{{/srv/active/svn/somemodule}}}, that would yield the following: 
     239 
     240{{{ #!ini 
    259241[trac] 
    260242authz_file = /path/to/svnaccessfile 
    261 authz_module_name = blahblah 
     243authz_module_name = somemodule 
    262244... 
    263 repository_dir = /srv/active/svn/blahblah  
    264 }}} 
    265  
    266 where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[blahblah:/some/path]}}}. 
     245repository_dir = /srv/active/svn/somemodule  
     246}}} 
     247 
     248where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[somemodule:/some/path]}}}. 
    267249 
    268250'''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac.  
     
    270252As of version 0.12, make sure you have ''!AuthzSourcePolicy'' included in the permission_policies list in trac.ini, otherwise the authz permissions file will be ignored. 
    271253 
    272 {{{  
     254{{{#!ini 
    273255[trac] 
    274256permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy 
     
    278260 
    279261The same access file is typically applied to the corresponding Subversion repository using an Apache directive like this: 
    280 {{{ 
     262{{{#!apache 
    281263<Location /repos> 
    282264  DAV svn 
     
    288270}}} 
    289271 
    290 For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess] 
     272For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess]. 
    291273 
    292274== Debugging permissions 
    293275In trac.ini set: 
    294 {{{ 
     276{{{#!ini 
    295277[logging] 
    296278log_file = trac.log 
     
    299281}}} 
    300282 
    301 And watch: 
    302 {{{ 
     283Display the trac.log to understand what checks are being performed: 
     284{{{#!sh 
    303285tail -n 0 -f log/trac.log | egrep '\[perm\]|\[authz_policy\]' 
    304286}}} 
    305287 
    306 to understand what checks are being performed. See the sourced documentation of the plugin for more info. 
    307  
     288See the sourced documentation of the plugin for more info. 
    308289 
    309290----