Changes between Version 1 and Version 2 of TracPermissions


Ignore:
Timestamp:
2010-06-14 04:25:44 (14 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracPermissions

    v1 v2  
    44Trac uses a simple, case sensitive, permission system to control what users can and can't access.
    55
    6 Permission privileges are managed using the [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin'' web interface.
     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.
    77
    88In 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.
    … …  
    1010Non-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.
    1111In 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".
     12
     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).
     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.
    1225
    1326== Available Privileges ==
    … …  
    2942|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
    3043|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
    31 || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field ||
    32 || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||
    33 || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field ||
     44|| `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 ||
     45|| `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. ||
     46|| `TICKET_EDIT_CC` || Full modify cc field ||
     47|| `TICKET_EDIT_DESCRIPTION` || Modify description field ||
     48|| `TICKET_EDIT_COMMENT` || Modify comments ||
     49|| `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. ||
    3450
    3551Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.
    … …  
    3753=== Roadmap ===
    3854
    39 || `MILESTONE_VIEW` || View a milestone ||
     55|| `MILESTONE_VIEW` || View milestones and assign tickets to milestones. ||
    4056|| `MILESTONE_CREATE` || Create a new milestone ||
    4157|| `MILESTONE_MODIFY` || Modify existing milestones ||
    4258|| `MILESTONE_DELETE` || Delete milestones ||
    4359|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
    44 || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292 ||
    45 || `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN ||
     60|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] ||
     61|| `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN ||
    4662
    4763=== Reports ===
    … …  
    7490|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
    7591|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||
    76 || `EMAIL_VIEW` || Shows email addresses even if [wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] ||
     92|| `EMAIL_VIEW` || Shows email addresses even if [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] ||
    7793
    7894== Granting Privileges ==
    … …  
    100116== Permission Groups ==
    101117
    102 There are two built-in groups, "authenticated" and "anonymous".[[BR]]
    103 Any user who has not logged in is automatically in the "anonymous" group.[[BR]]
    104 Any user who has logged in is also in the "authenticated" group.[[BR]]
    105 The "authenticated" group inherits permissions from the "anonymous" group.[[BR]]
    106 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.
     118There are two built-in groups, "authenticated" and "anonymous".
     119Any user who has not logged in is automatically in the "anonymous" group.
     120Any user who has logged in is also in the "authenticated" group.
     121The "authenticated" group inherits permissions from the "anonymous" group.
     122For example, if the "anonymous" group has permission WIKI_MODIFY,
     123it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well.
    107124
    108125Custom groups may be defined that inherit permissions from the two built-in groups.
    … …  
    117134}}}
    118135
    119 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'''.
     136Group 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'''.
    120137
    121138== Adding a New Group and Permissions ==
    … …  
    155172On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.
    156173
    157  '''anonymous'''::
     174'''anonymous'''
     175{{{
    158176 BROWSER_VIEW
    159177 CHANGESET_VIEW
    … …  
    167185 TICKET_VIEW
    168186 TIMELINE_VIEW
    169  WIKI_VIEW
     187 WIKI_VIEW
     188}}}
    170189
    171  '''authenticated'''::
     190'''authenticated'''
     191{{{
    172192 TICKET_CREATE
    173193 TICKET_MODIFY
    174194 WIKI_CREATE
    175195 WIKI_MODIFY 
    176 
     196}}}
    177197----
    178198See also: TracAdmin, TracGuide and TracFineGrainedPermissions