Changes between Version 1 and Version 2 of TracPermissions


Ignore:
Timestamp:
Aug 28, 2012, 12:26:52 AM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracPermissions

    v1 v2  
    22[[TracGuideToc]]
    33
    4 Trac uses a simple permission system to control what users can and can't access.
    5 
    6 Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool.
     4Trac uses a simple, case sensitive, permission system to control what users can and can't access.
     5
     6Permission privileges are managed using the [TracAdmin trac-admin] tool or (new in version 0.11) the ''General / Permissions'' panel in the ''Admin'' tab of the web interface.
     7
     8In addition to the default permission policy described in this page, it is possible to activate additional permission policies by enabling plugins and listing them in the `[trac] permission_policies` configuration entry in the TracIni. See TracFineGrainedPermissions for more details.
    79
    810Non-authenticated users accessing the system are assigned the name "anonymous". Assign permissions to the "anonymous" user to set privileges for anonymous/guest users. The parts of Trac that a user does not have the privileges for will not be displayed in the navigation.
    9 
    1011In addition to these privileges, users can be granted additional individual rights in effect when authenticated and logged into the system. All logged in users belong to the virtual group "authenticated", which inherits permissions from "anonymous".
    1112
     13== Graphical Admin Tab ==
     14''This feature is new in version 0.11.''
     15
     16To access this tab, a user must have `TRAC_ADMIN privileges`. This can be performed as follows (more on the trac-admin script below):
     17{{{
     18  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
     19}}}
     20
     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
    1229== Available Privileges ==
    1330
    14 To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system, it will allow you perform any operation.
    15 
    16 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac (note that the privilege names are case-sensitive):
     31To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system: it will allow you to perform any operation.
     32
     33Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''):
    1734
    1835=== Repository Browser ===
    … …  
    2845|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
    2946|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
    30 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field ||
    31 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||
    32 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field ||
     47|| `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 ||
     48|| `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. ||
     49|| `TICKET_EDIT_CC` || Full modify cc field ||
     50|| `TICKET_EDIT_DESCRIPTION` || Modify description field ||
     51|| `TICKET_EDIT_COMMENT` || Modify comments ||
     52|| `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. ||
     53
     54Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.
    3355
    3456=== Roadmap ===
    3557
    36 || `MILESTONE_VIEW` || View a milestone ||
     58|| `MILESTONE_VIEW` || View milestones and assign tickets to milestones. ||
    3759|| `MILESTONE_CREATE` || Create a new milestone ||
    3860|| `MILESTONE_MODIFY` || Modify existing milestones ||
    3961|| `MILESTONE_DELETE` || Delete milestones ||
    4062|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
    41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page ||
     63|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] ||
     64|| `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN ||
    4265
    4366=== Reports ===
    4467
    45 || `REPORT_VIEW` || View [wiki:TracReports reports] ||
     68|| `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. ||
    4669|| `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] ||
    4770|| `REPORT_CREATE` || Create new [wiki:TracReports reports] ||
    … …  
    5578|| `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages ||
    5679|| `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages ||
     80|| `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages ||
    5781|| `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments ||
    5882|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||
     83
     84=== Permissions ===
     85
     86|| `PERMISSION_GRANT` || add/grant a permission ||
     87|| `PERMISSION_REVOKE` || remove/revoke a permission ||
     88|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions ||
    5989
    6090=== Others ===
    … …  
    6393|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
    6494|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||
     95|| `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni 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.
    65100
    66101== Granting Privileges ==
    … …  
    81116}}}
    82117
     118Or add all privileges:
     119{{{
     120  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
     121}}}
     122
    83123== Permission Groups ==
     124
     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.
     131
     132Custom groups may be defined that inherit permissions from the two built-in groups.
    84133
    85134Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc.
    … …  
    92141}}}
    93142
    94 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'''.
     144
     145== Adding a New Group and Permissions ==
     146Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group.
     147
     148The following will add ''bob'' to the new group called ''beta_testers'' and then will assign WIKI_ADMIN permissions to that group. (Thus, ''bob'' will inherit the WIKI_ADMIN permission)
     149{{{
     150   $ trac-admin /path/to/projenv permission add bob beta_testers
     151   $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN
     152
     153}}}
    95154
    96155== Removing Permissions ==
    … …  
    107166You can also remove all privileges for a specific user:
    108167{{{
    109   $ trac-admin /path/to/projenv permission remove bob *
     168  $ trac-admin /path/to/projenv permission remove bob '*'
    110169}}}
    111170
    112171Or one privilege for all users:
    113172{{{
    114   $ trac-admin /path/to/projenv permission remove * REPORT_ADMIN
     173  $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN
    115174}}}
    116175
    117176== Default Permissions ==
    118177
    119 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in.
    120 
    121 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user.
    122 
     178By default on a new Trac installation, the `anonymous` user will have ''view'' access to everything in Trac, but will not be able to create or modify anything.
     179On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.
     180
     181'''anonymous'''
     182{{{
     183 BROWSER_VIEW
     184 CHANGESET_VIEW
     185 FILE_VIEW
     186 LOG_VIEW
     187 MILESTONE_VIEW
     188 REPORT_SQL_VIEW
     189 REPORT_VIEW
     190 ROADMAP_VIEW
     191 SEARCH_VIEW
     192 TICKET_VIEW
     193 TIMELINE_VIEW
     194 WIKI_VIEW
     195}}}
     196
     197'''authenticated'''
     198{{{
     199 TICKET_CREATE
     200 TICKET_MODIFY
     201 WIKI_CREATE
     202 WIKI_MODIFY 
     203}}}
    123204----
    124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]
     205See also: TracAdmin, TracGuide and TracFineGrainedPermissions