Changes between Version 4 and Version 5 of TracFineGrainedPermissions

Timestamp:

Oct 1, 2024, 10:09:59 PM (8 weeks ago)

Author:

trac

Comment:

--

TracFineGrainedPermissions

@@ -28 +28 @@
 * !LegacyAttachmentPolicy uses the coarse-grained permissions to check permissions on attachments.
 
-Among the optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See
-[trac:source:branches/1.4-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.
+Among the optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See [trac:source:branches/1.4-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.
 
 Another permission policy [#AuthzSourcePolicy], uses the [http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html path-based authorization] defined by Subversion to enforce permissions on the version control system.
@@ -37 +36 @@
 === !AuthzPolicy
 ==== Configuration
-* Put an empty conf file (`authzpolicy.conf`) in a secure location on the server, not readable by users other than the webuser. If the  file contains non-ASCII characters, the UTF-8 encoding should be used.
+
+* Put an empty conf file (`authzpolicy.conf`) in a secure location on the server, not readable by users other 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-permission_policies-option permission_policies] option in the `[trac]` section:
@@ -61 +61 @@
 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.
+'''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:
@@ -100 +100 @@
 The username will match any of 'anonymous', 'authenticated', <username> 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:#5648] for details about this missing feature. ||
+'''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:#5648] for details about this missing feature.
 
 For example, if the `authz_file` contains:
@@ -184 +184 @@
 
 ==== Missing Features
+
 Although possible with the !DefaultPermissionPolicy handling (see Admin panel), fine-grained permissions still miss those grouping features (see [trac:#9573], [trac:#5648]). Patches are partially available, see authz_policy.2.patch, part of [trac:ticket:6680 #6680].
 
@@ -199 +200 @@
 [groups]
 permission_level_1 = WIKI_VIEW, TICKET_VIEW
-permission_level_2  = permission_level_1, WIKI_MODIFY, TICKET_MODIFY
+permission_level_2 = permission_level_1, WIKI_MODIFY, TICKET_MODIFY
 [*]
 @team1 = permission_level_1
@@ -206 +207 @@
 }}}
 
-=== !AuthzSourcePolicy  (`mod_authz_svn`-like permission policy) #AuthzSourcePolicy
+=== !AuthzSourcePolicy (`mod_authz_svn`-like permission policy) #AuthzSourcePolicy
 
 `AuthzSourcePolicy` can be used for restricting access to the repository. Granular permission control needs a definition file, which is the one used by Subversion's `mod_authz_svn`.
@@ -319 +320 @@
 
 == Debugging permissions
+
 In trac.ini set:
 {{{#!ini