Changes between Version 1 and Version 2 of TracFineGrainedPermissions

Timestamp:

Feb 8, 2011, 3:06:30 PM (14 years ago)

Author:

trac

Comment:

--

TracFineGrainedPermissions

@@ -10 +10 @@
 
 An example policy based on an Authz-style system has been added. See
-[source:trunk/sample-plugins/permissions/authz_policy.py] for details. (See also [source:trunk/sample-plugins/permissions] for more samples.)
+[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).
@@ -16 +16 @@
  - 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.
  - 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
+{{{
 [authz_policy]
 authz_file = /some/trac/env/conf/authzpolicy.conf
-
+}}}
+   3. enable the single file plugin
+{{{
 [components]
 ...
-authz_policy = enabled
+authz_policy.* = enabled
 }}}
 
@@ -61 +66 @@
 === 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 differences.
+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.
 
 That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn. 
-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)].
+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.
 
 Example:
@@ -117 +122 @@
 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.
+
 ----
 See also: TracPermissions
+http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin for a simple editor plugin.