Changes between Version 1 and Version 2 of TracFineGrainedPermissions
- Timestamp:
- 2010-06-14 04:25:44 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFineGrainedPermissions
v1 v2 5 5 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. 6 6 7 Note that for Trac 0.12, `authz_policy` has been integrated in trunk branch as `tracopt.perm.authz_policy.*` 8 7 9 == Permission Policies == 8 10 … … 10 12 11 13 An example policy based on an Authz-style system has been added. See 12 [ source:trunk/sample-plugins/permissions/authz_policy.py] for details. (See also [source:trunk/sample-plugins/permissions] for more samples.)14 [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.) 13 15 14 16 - Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (required). 15 - Copy this file in your plugins directory16 - P lonk a [http://swapoff.org/files/authzpolicy.conf authzpolicy.conf] file somewhere. FIXME: what does ''plonk'' mean? ;-)17 - Copy authz_policy.py into your plugins directory. 18 - 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. 17 19 - Update your `trac.ini`: 20 1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section 18 21 {{{ 19 22 [trac] 20 23 ... 21 permission_policies = AuthzPolicy, DefaultPermissionPolicy 22 24 permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy 25 }}} 26 2. add a new `[authz_policy]` section 27 {{{ 23 28 [authz_policy] 24 29 authz_file = /some/trac/env/conf/authzpolicy.conf 25 30 }}} 31 3. enable the single file plugin 32 {{{ 26 33 [components] 27 34 ... 28 authz_policy = enabled35 authz_policy.* = enabled 29 36 }}} 30 37 … … 40 47 {{{ 41 48 [wiki:WikiStart@*] 42 * = VIEW49 * = WIKI_VIEW 43 50 44 51 [wiki:PrivatePage@*] 45 john = VIEW52 john = WIKI_VIEW 46 53 * = 47 54 }}} … … 61 68 === mod_authz_svn-like permission policy === 62 69 63 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 s.70 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. 64 71 65 72 That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn. 66 More information about this file format and about its usage in Subversion is available in the [http://svnbook.red-bean.com/svnbook/book.html#svn-ch-6-sect-4.4.2 Subversion Book (Per-Directory Access Control)].73 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. 67 74 68 75 Example: … … 92 99 }}} 93 100 94 if you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add101 If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add 95 102 96 103 {{{ … … 98 105 }}} 99 106 100 where ''modulename'' refers to the same repository indicated by the `repository_dir` entry in the `[trac]` section. 107 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: 108 109 {{{ 110 [trac] 111 authz_file = /path/to/svnaccessfile 112 authz_module_name = blahblah 113 ... 114 repository_dir = /srv/active/svn/blahblah 115 }}} 116 117 where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[blahblah:/some/path]}}}. 101 118 102 119 '''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac. … … 117 134 For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess] 118 135 136 == Getting TracFineGrainedPermissions to work == 137 138 Don't forget to restart Trac engine to apply new configuration if you are running tracd standalone server. 139 119 140 ---- 120 See also: TracPermissions 141 See also: TracPermissions, 142 [http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin TracHacks:FineGrainedPageAuthzEditorPlugin] for a simple editor plugin.
