Changes between Version 1 and Version 2 of TracPermissions


Ignore:
Timestamp:
Oct 18, 2009, 5:01:52 PM (14 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.
     4Trac uses a simple, case sensitive, permission system to control what users can and can't access.
    55
    6 Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool.
     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.
     11In 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".
    912
    10 In 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".
     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 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
     23
     24An 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.
    1125
    1226== Available Privileges ==
    1327
    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.
     28To 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.
    1529
    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):
     30Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''):
    1731
    1832=== Repository Browser ===
     
    2842|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
    2943|| `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 ||
     44|| `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 ||
    3145|| `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||
     46|| `TICKET_EDIT_CC` || Full modify cc field ||
     47|| `TICKET_EDIT_DESCRIPTION` || Modify description field ||
    3248|| `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field ||
     49
     50Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.
    3351
    3452=== Roadmap ===
     
    3957|| `MILESTONE_DELETE` || Delete milestones ||
    4058|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
    41 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page ||
     59|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292 ||
     60|| `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN ||
    4261
    4362=== Reports ===
    4463
    45 || `REPORT_VIEW` || View [wiki:TracReports reports] ||
     64|| `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. ||
    4665|| `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] ||
    4766|| `REPORT_CREATE` || Create new [wiki:TracReports reports] ||
     
    5877|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||
    5978
     79=== Permissions ===
     80
     81|| `PERMISSION_GRANT` || add/grant a permission ||
     82|| `PERMISSION_REVOKE` || remove/revoke a permission ||
     83|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions ||
     84
     85
    6086=== Others ===
    6187
     
    6389|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
    6490|| `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 [wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] ||
    6592
    6693== Granting Privileges ==
     
    81108}}}
    82109
     110Or add all privileges:
     111{{{
     112  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
     113}}}
     114
    83115== Permission Groups ==
     116
     117There are two built-in groups, "authenticated" and "anonymous".[[BR]]
     118Any user who has not logged in is automatically in the "anonymous" group.[[BR]]
     119Any user who has logged in is also in the "authenticated" group.[[BR]]
     120The "authenticated" group inherits permissions from the "anonymous" group.[[BR]]
     121eg. if the "anonymous" group has permission WIKI_MODIFY, it's not necessary to add the WIKI_MODIFY permisison to the "authenticated" group as well.
     122
     123Custom groups may be defined that inherit permissions from the two built-in groups.
    84124
    85125Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc.
     
    92132}}}
    93133
    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.
     134Group 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'''.
     135
     136== Adding a New Group and Permissions ==
     137Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group.
     138
     139The 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)
     140{{{
     141   $ trac-admin /path/to/projenv permission add bob beta_testers
     142   $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN
     143
     144}}}
    95145
    96146== Removing Permissions ==
     
    107157You can also remove all privileges for a specific user:
    108158{{{
    109   $ trac-admin /path/to/projenv permission remove bob *
     159  $ trac-admin /path/to/projenv permission remove bob '*'
    110160}}}
    111161
    112162Or one privilege for all users:
    113163{{{
    114   $ trac-admin /path/to/projenv permission remove * REPORT_ADMIN
     164  $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN
    115165}}}
    116166
    117167== Default Permissions ==
    118168
    119 Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in.
     169By 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.
     170On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.
    120171
    121 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user.
     172 '''anonymous'''::
     173 BROWSER_VIEW
     174 CHANGESET_VIEW
     175 FILE_VIEW
     176 LOG_VIEW
     177 MILESTONE_VIEW
     178 REPORT_SQL_VIEW
     179 REPORT_VIEW
     180 ROADMAP_VIEW
     181 SEARCH_VIEW
     182 TICKET_VIEW
     183 TIMELINE_VIEW
     184 WIKI_VIEW
     185
     186 '''authenticated'''::
     187 TICKET_CREATE
     188 TICKET_MODIFY
     189 WIKI_CREATE
     190 WIKI_MODIFY 
    122191
    123192----
    124 See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]
     193See also: TracAdmin, TracGuide and TracFineGrainedPermissions