Free cookie consent management tool by TermsFeed Policy Generator

# Changes between Version 2 and Version 3 of TracFineGrainedPermissions

Ignore:
Timestamp:
06/05/14 14:37:16 (9 years ago)
Comment:

--

### Legend:

Unmodified
 v2 [[PageOutline(2-5, Contents, floated)]] = Fine grained permissions = Before Trac 0.11, it was only possible to define fine-grained permissions checks on the repository browser sub-system. 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. Note that for Trac 0.12, authz_policy has been integrated in trunk branch as tracopt.perm.authz_policy.* 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. 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. == Permission Policies == === !AuthzPolicy === An example policy based on an Authz-style system has been added. See [trac:source:branches/0.11-stable/sample-plugins/permissions/authz_policy.py authz_policy.py] for details (current version requires >= Python 2.4). (See also [trac:source:branches/0.11-stable/sample-plugins/permissions sample-plugins/permissions] for more samples.) - Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (required). - Copy authz_policy.py into your plugins directory. - 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. - Update your trac.ini: 1. modify the [TracIni#trac-section permission_policies] entry in the [trac] section A great diversity of permission policies can be implemented, and Trac comes with a few examples. Which policies are currently active is determined by a configuration setting in TracIni: e.g. {{{ [trac] permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy }}} This 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. Among the possible optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See [trac:source:branches/0.12-stable/tracopt/perm/authz_policy.py authz_policy.py] for details. Another 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. See also [trac:source:branches/0.12-stable/sample-plugins/permissions sample-plugins/permissions] for more examples. === !AuthzPolicy === ==== Configuration ==== * Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (still needed for 0.12). * Copy authz_policy.py into your plugins directory (only for Trac 0.11). * 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. * Update your trac.ini: 1. modify the [TracIni#trac-section permission_policies] entry in the [trac] section {{{ [trac] permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy }}} 2. add a new [authz_policy] section 1. add a new [authz_policy] section {{{ [authz_policy] authz_file = /some/trac/env/conf/authzpolicy.conf }}} 3. enable the single file plugin 1. enable the plugin through [/admin/general/plugin WebAdmin] or by editing the [components] section {{{ [components] ... authz_policy.* = enabled }}} # Trac 0.12 tracopt.perm.authz_policy.* = enabled # for Trac 0.11 use this #authz_policy.* = enabled }}} ==== Usage Notes ==== Note that the order in which permission policies are specified is quite critical, as policies will be examined in the sequence provided. A policy will return either True, False or None for a given permission check. Only if the return value is None will the ''next'' permission policy be consulted. If no policy explicitly grants the permission, the final result will be False (i.e. no permission). A 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. NOTE: 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). The authzpolicy.conf file is a .ini style configuration file: {{{ [wiki:PrivatePage@*] john = WIKI_VIEW, !WIKI_MODIFY jack = WIKI_VIEW * = }}} * Each section of the config is a glob pattern used to match against a Trac resource descriptor. These descriptors are in the form: {{{ :@[/:@ ...] }}} Resources are ordered left to right, from parent to child. If any component is inapplicable, * is substituted. If the version pattern is not specified explicitely, all versions (@*) is added implicitly Example: Match the WikiStart page {{{ [wiki:*] [wiki:WikiStart*] [wiki:WikiStart@*] [wiki:WikiStart] }}} Example: Match the attachment wiki:WikiStart@117/attachment/FOO.JPG@* on WikiStart {{{ [wiki:*] [wiki:WikiStart*] [wiki:WikiStart@*] [wiki:WikiStart@*/attachment/*] [wiki:WikiStart@117/attachment/FOO.JPG] }}} * Sections are checked against the current Trac resource descriptor '''IN ORDER''' of appearance in the configuration file. '''ORDER IS CRITICAL'''. * Once a section matches, the current username is matched against the keys (usernames) of the section, '''IN ORDER'''. * If a key (username) is prefixed with a @, it is treated as a group. * If a value (permission) is prefixed with a !, the permission is denied rather than granted. The username will match any of 'anonymous', 'authenticated', 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 || For example, if the authz_file contains: [wiki:PrivatePage@*] john = WIKI_VIEW * = * = !WIKI_VIEW }}} and the default permissions are set like this: Then: - All versions of WikiStart will be viewable by everybody (including anonymous) - !PrivatePage will be viewable only by john - other pages will be viewable only by john and jack === mod_authz_svn-like permission policy === At the time of this writing, the old fine grained permissions system from Trac 0.10 and before used for restricting access to the repository has not yet been converted to a permission policy component, but from the user point of view, this makes little if no difference. * All versions of WikiStart will be viewable by everybody (including anonymous) * !PrivatePage will be viewable only by john * other pages will be viewable only by john and jack Groups: {{{ [groups] admins = john, jack devs = alice, bob [wiki:Dev@*] @admins = TRAC_ADMIN @devs = WIKI_VIEW * = [*] @admins = TRAC_ADMIN * = }}} Then: - everything is blocked (whitelist approach), but - admins get all TRAC_ADMIN everywhere and - devs can view wiki pages. Some repository examples (Browse Source specific): {{{ # A single repository: [repository:test_repo@*] john = BROWSER_VIEW, FILE_VIEW # John has BROWSER_VIEW and FILE_VIEW for the entire test_repo # All repositories: [repository:*@*] jack = BROWSER_VIEW, FILE_VIEW # John has BROWSER_VIEW and FILE_VIEW for all repositories }}} Very fine grain repository access: {{{ # John has BROWSER_VIEW and FILE_VIEW access to trunk/src/some/location/ only [repository:test_repo@*/source:trunk/src/some/location/*@*] john = BROWSER_VIEW, FILE_VIEW # John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of all files at trunk/src/some/location only [repository:test_repo@*/source:trunk/src/some/location/*@1] john = BROWSER_VIEW, FILE_VIEW # John has BROWSER_VIEW and FILE_VIEW access to all revisions of 'somefile' at trunk/src/some/location only [repository:test_repo@*/source:trunk/src/some/location/somefile@*] john = BROWSER_VIEW, FILE_VIEW # John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of 'somefile' at trunk/src/some/location only [repository:test_repo@*/source:trunk/src/some/location/somefile@1] john = BROWSER_VIEW, FILE_VIEW }}} Note: In order for Timeline to work/visible for John, we must add CHANGESET_VIEW to the above permission list. ==== Missing Features ==== 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]). You cannot do the following: {{{ [groups] team1 = a, b, c team2 = d, e, f team3 = g, h, i departmentA = team1, team2 }}} Permission groups are not supported either. You cannot do the following: {{{ [groups] permission_level_1 = WIKI_VIEW, TICKET_VIEW permission_level_2  = permission_level_1, WIKI_MODIFY, TICKET_MODIFY [*] @team1 = permission_level_1 @team2 = permission_level_2 @team3 = permission_level_2, TICKET_CREATE }}} === !AuthzSourcePolicy  (mod_authz_svn-like permission policy) === #AuthzSourcePolicy 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. That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn. '''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac. As 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. {{{ [trac] permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy }}} ==== Subversion Configuration ==== For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess] == Getting TracFineGrainedPermissions to work == Don't forget to restart Trac engine to apply new configuration if you are running tracd standalone server. == Debugging permissions In trac.ini set: {{{ [logging] log_file = trac.log log_level = DEBUG log_type = file }}} And watch: {{{ tail -n 0 -f log/trac.log | egrep '$perm$|$authz_policy$' }}} to understand what checks are being performed. See the sourced documentation of the plugin for more info. ----