Changes between Version 1 and Version 2 of TracPermissions


Ignore:
Timestamp:
12/04/17 13:27:54 (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracPermissions

    v1 v2  
    1414''This feature is new in version 0.11.'' 
    1515 
    16 To access this tab, a user must have `TRAC_ADMIN privileges`. This can be performed as follows (more on the trac-admin script below): 
     16To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_ADD`, `PERMISSION_REMOVE`. The permissions can granted using the `trac-admin` command (more on `trac-admin` below): 
    1717{{{ 
    1818  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 
    1919}}} 
    2020 
    21 Then, the user `bob` will be able to see the Admin tab, and can then access the permissions menu. This menu will allow you to perform all the following actions, but from the browser without requiring root access to the server (just the correct permissions for your user account). 
    22  
     21Then, the user `bob` will be able to see the Admin tab, and can then access the permissions menu. This menu will allow you to perform all the following actions, but from the browser without requiring root access to the server (just the correct permissions for your user account). '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.''' 
     22 
     23 1. [[Image(htdocs:../common/guide/admin.png)]] 
     24 1. [[Image(htdocs:../common/guide/admin-permissions.png)]] 
     25 1. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]] 
    2326 
    2427An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [http://trac-hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user. 
    … …  
    4649|| `TICKET_EDIT_CC` || Full modify cc field || 
    4750|| `TICKET_EDIT_DESCRIPTION` || Modify description field || 
     51|| `TICKET_EDIT_COMMENT` || Modify comments || 
    4852|| `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the reporter and description fields. It also allows managing ticket properties in the WebAdmin panel. || 
    4953 
    … …  
    7478|| `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages || 
    7579|| `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages || 
     80|| `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages || 
    7681|| `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments || 
    7782|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 
    … …  
    8388|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 
    8489 
    85  
    8690=== Others === 
    8791 
    … …  
    8993|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 
    9094|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || 
    91 || `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] || 
     95|| `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false || 
     96 
     97== Creating New Privileges == 
     98 
     99To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation of the component in the admin panel. 
    92100 
    93101== Granting Privileges == 
    … …  
    115123== Permission Groups == 
    116124 
    117 There are two built-in groups, "authenticated" and "anonymous".[[BR]] 
    118 Any user who has not logged in is automatically in the "anonymous" group.[[BR]] 
    119 Any user who has logged in is also in the "authenticated" group.[[BR]] 
    120 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]] 
    121 eg. if the "anonymous" group has permission WIKI_MODIFY, it's not necessary to add the WIKI_MODIFY permisison to the "authenticated" group as well. 
     125There are two built-in groups, "authenticated" and "anonymous". 
     126Any user who has not logged in is automatically in the "anonymous" group. 
     127Any user who has logged in is also in the "authenticated" group. 
     128The "authenticated" group inherits permissions from the "anonymous" group. 
     129For example, if the "anonymous" group has permission WIKI_MODIFY,  
     130it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 
    122131 
    123132Custom groups may be defined that inherit permissions from the two built-in groups. 
    … …  
    132141}}} 
    133142 
    134 Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use lowercase for group names, as uppercase is reserved for permissions'''. 
     143Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use at least one lowercase character in group names, as all-uppercase names are reserved for permissions'''. 
    135144 
    136145== Adding a New Group and Permissions ==