Changes between Initial Version and Version 1 of TracFineGrainedPermissions

06/08/12 10:47:01 (11 years ago)



  • TracFineGrainedPermissions

    v1 v1  
     1= Fine grained permissions =
     3Before Trac 0.11, it was only possible to define fine-grained permissions checks on the repository browser sub-system.
     5Since 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.
     7Note that for Trac 0.12, `authz_policy` has been integrated in trunk branch as `tracopt.perm.authz_policy.*`
     9== Permission Policies ==
     11=== !AuthzPolicy ===
     13An example policy based on an Authz-style system has been added. See
     14[trac:source:branches/0.11-stable/sample-plugins/permissions/] 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.)
     16 - Install [ ConfigObj] (required).
     17 - Copy into your plugins directory.
     18 - Put a [ 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.
     19 - Update your `trac.ini`:
     20   1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section
     24permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
     26   2. add a new `[authz_policy]` section
     29authz_file = /some/trac/env/conf/authzpolicy.conf
     31   3. enable the single file plugin
     35authz_policy.* = enabled
     38Note that the order in which permission policies are specified is quite critical,
     39as policies will be examined in the sequence provided.
     41A policy will return either `True`, `False` or `None` for a given permission check.
     42Only if the return value is `None` will the ''next'' permission policy be consulted.
     43If no policy explicitly grants the permission, the final result will be `False`
     44(i.e. no permission).
     46For example, if the `authz_file` contains:
     49* = WIKI_VIEW
     52john = WIKI_VIEW
     53* =
     55and the default permissions are set like this:
     57john           WIKI_VIEW
     58jack           WIKI_VIEW
     59# anonymous has no WIKI_VIEW
     63 - All versions of WikiStart will be viewable by everybody (including anonymous)
     64 - !PrivatePage will be viewable only by john
     65 - other pages will be viewable only by john and jack
     68=== mod_authz_svn-like permission policy ===
     70At 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.
     72That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn.
     73More information about this file format and about its usage in Subversion is available in the  [ Path-Based Authorization] section in the Server Configuration chapter of the svn book.
     78* = r
     81harry = rw
     82sally = r
     85harry =
     88 * '''/''' = ''Everyone has read access by default''
     89 * '''/branches/calc/bug-142''' = ''harry has read/write access, sally read only''
     90 * '''/branches/calc/bug-142/secret''' = ''harry has no access, sally has read access (inherited as a sub folder permission)''
     92==== Trac Configuration ====
     94To 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.
     98authz_file = /path/to/svnaccessfile
     101If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add
     104authz_module_name = modulename
     107where ''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:
     111authz_file = /path/to/svnaccessfile
     112authz_module_name = blahblah
     114repository_dir = /srv/active/svn/blahblah
     117where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[blahblah:/some/path]}}}.
     119'''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac.
     121==== Subversion Configuration ====
     123The same access file is typically applied to the corresponding Subversion repository using an Apache directive like this:
     125<Location /repos>
     126  DAV svn
     127  SVNParentPath /usr/local/svn
     129  # our access control policy
     130  AuthzSVNAccessFile /path/to/svnaccessfile
     134For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess]
     136== Getting TracFineGrainedPermissions to work ==
     138Don't forget to restart Trac engine to apply new configuration if you are running tracd standalone server.
     141See also: TracPermissions,
     142[ TracHacks:FineGrainedPageAuthzEditorPlugin] for a simple editor plugin.