Changes between Version 2 and Version 3 of TracFineGrainedPermissions
- Timestamp:
- May 6, 2010, 11:40:54 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFineGrainedPermissions
v2 v3 4 4 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 7 Note that for Trac 0.12, `authz_policy` has been integrated in trunk branch as `tracopt.perm.authz_policy.*` 6 8 7 9 == Permission Policies == … … 97 99 }}} 98 100 99 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 100 102 101 103 {{{ … … 103 105 }}} 104 106 105 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]}}}. 106 118 107 119 '''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac.