Changes between Version 1 and Version 2 of TracPermissions


Ignore:
Timestamp:
Feb 5, 2016, 1:02:47 PM (8 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_GRANT`, `PERMISSION_REVOKE`. The permissions can be 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 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)]]
     26
     27An 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.
     28
     29From the graphical admin tab, users with `PERMISSION_GRANT` will only be allowed to grant permissions that they possess, and users with `PERMISSION_REVOKE` will only be allowed to revoke permissions that they possess. For example, a user cannot grant `MILESTONE_ADMIN` unless they have `PERMISSION_GRANT` and `MILESTONE_ADMIN`, and they cannot revoke `MILESTONE_ADMIN` unless they have `PERMISSION_REVOKE` and `MILESTONE_ADMIN`. `PERMISSION_ADMIN` just grants the user both `PERMISSION_GRANT` and `PERMISSION_REVOKE`, and users with `TRAC_ADMIN` can grant or revoke any permission.
    2330
    2431== Available Privileges ==
    … …  
    4047|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
    4148|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
    42 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field, cc field add/remove when logged in or set email to pref ||
    43 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||
     49|| `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description field, add/remove other users from cc field when logged in, and set email to pref ||
     50|| `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets]. Tickets can be assigned to users through a [TracTickets#Assign-toasDrop-DownList drop-down list] when the list of possible owners has been restricted. ||
    4451|| `TICKET_EDIT_CC` || Full modify cc field ||
    4552|| `TICKET_EDIT_DESCRIPTION` || Modify description field ||
    46 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field ||
     53|| `TICKET_EDIT_COMMENT` || Modify comments ||
     54|| `TICKET_BATCH_MODIFY` || [wiki:TracBatchModify Batch modify] tickets ||
     55|| `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. ||
    4756
    4857Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.
    … …  
    5059=== Roadmap ===
    5160
    52 || `MILESTONE_VIEW` || View a milestone ||
     61|| `MILESTONE_VIEW` || View milestones and assign tickets to milestones. ||
    5362|| `MILESTONE_CREATE` || Create a new milestone ||
    5463|| `MILESTONE_MODIFY` || Modify existing milestones ||
    5564|| `MILESTONE_DELETE` || Delete milestones ||
    5665|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
    57 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292 ||
    58 || `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN ||
     66|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] ||
     67|| `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN ||
    5968
    6069=== Reports ===
    … …  
    7281|| `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages ||
    7382|| `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages ||
     83|| `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages ||
    7484|| `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments ||
    7585|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||
    … …  
    8191|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions ||
    8292
    83 
    8493=== Others ===
    8594
    … …  
    8796|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
    8897|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||
    89 || `EMAIL_VIEW` || Shows email addresses even if [wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] ||
     98|| `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false ||
     99
     100== Creating New Privileges ==
     101
     102To 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  on the [wiki:TracIni#extra-permissions-section TracIni] page after enabling the component.
    90103
    91104== Granting Privileges ==
    … …  
    113126== Permission Groups ==
    114127
    115 There are two built-in groups, "authenticated" and "anonymous".[[BR]]
    116 Any user who has not logged in is automatically in the "anonymous" group.[[BR]]
    117 Any user who has logged in is also in the "authenticated" group.[[BR]]
    118 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]]
    119 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.
     128There are two built-in groups, "authenticated" and "anonymous".
     129Any user who has not logged in is automatically in the "anonymous" group.
     130Any user who has logged in is also in the "authenticated" group.
     131The "authenticated" group inherits permissions from the "anonymous" group.
     132For example, if the "anonymous" group has permission WIKI_MODIFY,
     133it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well.
    120134
    121135Custom groups may be defined that inherit permissions from the two built-in groups.
    … …  
    130144}}}
    131145
    132 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'''.
     146Group 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'''.
    133147
    134148== Adding a New Group and Permissions ==
    … …  
    168182On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.
    169183
    170  '''anonymous'''::
     184'''anonymous'''
     185{{{
    171186 BROWSER_VIEW
    172187 CHANGESET_VIEW
    … …  
    180195 TICKET_VIEW
    181196 TIMELINE_VIEW
    182  WIKI_VIEW
    183 
    184  '''authenticated'''::
     197 WIKI_VIEW
     198}}}
     199
     200'''authenticated'''
     201{{{
    185202 TICKET_CREATE
    186203 TICKET_MODIFY
    187204 WIKI_CREATE
    188205 WIKI_MODIFY 
    189 
     206}}}
    190207----
    191208See also: TracAdmin, TracGuide and TracFineGrainedPermissions