Changes between Version 8 and Version 9 of TracPermissions


Ignore:
Timestamp:
10/05/2023 07:15:52 AM (7 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracPermissions

    v8 v9  
    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 [TracIni#trac-permission_policies-option "[trac] permission_policies"]. See TracFineGrainedPermissions for more details.
    99
    10 Non-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 privilege for will not be displayed in the navigation.
     10Non-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 privileges for will not be displayed in the navigation bar.
    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//.
    1212
    1313== Graphical Admin Tab
    1414
    15 To 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):
     15To 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 with a more detailed description [#GrantingPrivileges below]:
    1616{{{#!sh
    1717$ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
    1818}}}
    1919
    20 Then, the user `bob` will be able to see the Admin tab, and can access the permissions menu. This menu will allow you to perform all the following actions, but from the browser rather than requiring root access to the server. '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.'''
     20Then, the user `bob` will be able to see the Admin tab, and can access the permissions menu. This menu allows you to perform the following actions, but from the browser rather than requiring root access to the server. '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.'''
    2121
    2222[[Image(htdocs:../common/guide/admin.png)]]
    … …  
    3030== Available Privileges
    3131
    32 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 to perform any operation.
    33 
    34 Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''):
     32To enable all privileges for a user, use the `TRAC_ADMIN` permission. This permission is like being `root` on a *NIX system: it will allow you to perform any operation on Trac.
     33
     34Otherwise, individual privileges can be assigned to users for the different functional areas of Trac and '''note that the privilege names are uppercase''':
    3535
    3636=== Repository Browser
    … …  
    4545|| `TICKET_VIEW` || View existing [TracTickets tickets] and perform [TracQuery ticket queries] ||
    4646|| `TICKET_CREATE` || Create new [TracTickets tickets] ||
    47 || `TICKET_APPEND` || Add comments and attachments to [TracTickets tickets], and edit description of ticket the user created ||
     47|| `TICKET_APPEND` || Add comments and attachments to [TracTickets tickets], and edit description of ticket that the user created ||
    4848|| `TICKET_CHGPROP` || Modify [TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description of tickets created by others, add/remove other users from cc field when logged in ||
    4949|| `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [TracTickets tickets] in the [TracWorkflow default workflow]. Tickets can be assigned to users through a [TracTickets#Assign-toasDrop-DownList drop-down list] when the list of possible owners has been restricted. ||
    … …  
    5252|| `TICKET_EDIT_COMMENT` || Modify another user's comments. Any user can modify their own comments by default. ||
    5353|| `TICKET_BATCH_MODIFY` || [TracBatchModify Batch modify] tickets ||
    54 || `TICKET_ADMIN` || All `TICKET_*` permissions, deletion of ticket attachments and modification of the reporter field, which grants ability to create a ticket on behalf of another user (it will appear that another user created the ticket). It also allows managing ticket properties through the web administration module. ||
     54|| `TICKET_ADMIN` || All `TICKET_*` permissions, deletion of ticket attachments and modification of the reporter field, which grants ability to create a ticket on behalf of another user and it will appear that another user created the ticket. It also allows managing ticket properties through the web administration module. ||
    5555
    5656=== Roadmap
    … …  
    6262|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
    6363|| `ROADMAP_VIEW` || View the [TracRoadmap roadmap] page, which 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 ||
     64|| `ROADMAP_ADMIN` || To be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN ||
    6565
    6666=== Reports
    … …  
    9797== Attachment Permissions
    9898
    99 Attachment permissions are handled by `LegacyAttachmentPolicy`, and unlike the permissions discussed so far, the permissions provided by `LegacyAttachmentPolicy` are not directly granted. Rather, the ability to create, view and delete attachments is determined by the attachment's parent realm and permissions the user possesses for that realm.
    100 
    101 The attachment actions are determined by the following
    102 permissions in the ticket, wiki and milestone realms:
     99Attachment permissions are handled by `LegacyAttachmentPolicy`, and unlike the permissions discussed so far, the permissions provided by `LegacyAttachmentPolicy` are not directly granted. Rather, the ability to create, view and delete attachments is determined by the attachment's parent realm and permissions that the user possesses for that realm.
     100
     101The attachment actions are determined by the following permissions in the ticket, wiki and milestone realms:
    103102{{{#!table class="listing"
    104103||= Granted By: =||= Ticket =||= Wiki =||= Milestone =||
    … …  
    108107}}}
    109108
    110 If explicit attachment permissions are preferred, `ATTACHMENT_CREATE`, `ATTACHMENT_DELETE` and `ATTACHMENT_VIEW` can be created using the [trac:ExtraPermissionsProvider]. The simplest implementation is to simply define the actions.
     109An authenticated user can delete an attachment //they added// without possessing the permission that grants `ATTACHMENT_DELETE`.
     110
     111If explicit attachment permissions are preferred, then `ATTACHMENT_CREATE`, `ATTACHMENT_DELETE` and `ATTACHMENT_VIEW` can be created using the [trac:ExtraPermissionsProvider]. The simplest implementation is to simply define the actions:
    111112{{{#!ini
    112113[extra-permissions]
    … …  
    114115}}}
    115116
    116 An alternative configuration adds an `ATTACHMENT_ADMIN` meta-permission that grants the other 3 permission.
     117An alternative configuration adds an `ATTACHMENT_ADMIN` meta-permission that grants the other 3 permissions:
    117118{{{#!ini
    118119[extra-permissions]
    … …  
    120121}}}
    121122
    122 The explicit permissions can be used in concert with `LegacyAttachmentPolicy`, or `LegacyAttachmentPolicy` can be removed from `permission_policies`, in which case only users that have been explicitly granted the corresponding attachment actions will be able to create, delete and view attachments.
     123The explicit permissions can be used in conjunction with `LegacyAttachmentPolicy`, or `LegacyAttachmentPolicy` can be removed from `permission_policies`, in which case only users that have been explicitly granted the corresponding attachment actions will be able to create, delete and view attachments.
    123124
    124125== Granting Privileges
    125126
    126 You grant privileges to users using [TracAdmin trac-admin]. The current set of privileges can be listed with the following command:
     127Privileges are granted to users through [TracAdmin trac-admin]. The current set of privileges can be listed with the following command:
    127128{{{#!sh
    128129$ trac-admin /path/to/projenv permission list
    … …  
    150151Any user who has logged in is also in the //authenticated// group.
    151152The //authenticated// group inherits permissions from the //anonymous// group.
    152 For example, if the //anonymous// group has permission WIKI_MODIFY,
    153 it is not necessary to add the WIKI_MODIFY permission to the //authenticated// group as well.
     153For example, if the //anonymous// group has permission `WIKI_MODIFY`, it is not necessary to add the `WIKI_MODIFY` permission to the //authenticated// group as well.
    154154
    155155Custom groups may be defined that inherit permissions from the two built-in groups.
    … …  
    167167
    168168== Adding a New Group and Permissions
     169
    169170Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group.
    170171
    171 The 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)
     172The 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.
    172173{{{#!sh
    173174$ trac-admin /path/to/projenv permission add bob beta_testers
    … …  
    177178== Removing Permissions
    178179
    179 Permissions can be removed using the 'remove' command. For example:
     180Permissions can be removed using the 'remove' command.
    180181
    181182This command will prevent the user ''bob'' from deleting reports:
    … …  
    202203== Default Permissions
    203204
    204 By 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.
    205 On the other hand, the //authenticated// users will have the permissions to ''create and modify tickets and wiki pages''.
     205By default on a new Trac installation, the //anonymous// user has ''view'' access to everything in Trac, but is not able to create or modify anything.
     206The //authenticated// user has the permissions to ''create and modify tickets and wiki pages''.
    206207
    207208//**anonymous**//
    208209{{{
    209 BROWSER_VIEW 
    210 CHANGESET_VIEW 
    211 FILE_VIEW 
    212 LOG_VIEW 
    213 MILESTONE_VIEW 
    214 REPORT_SQL_VIEW 
    215 REPORT_VIEW 
    216 ROADMAP_VIEW 
    217 SEARCH_VIEW 
    218 TICKET_VIEW 
     210BROWSER_VIEW
     211CHANGESET_VIEW
     212FILE_VIEW
     213LOG_VIEW
     214MILESTONE_VIEW
     215REPORT_SQL_VIEW
     216REPORT_VIEW
     217ROADMAP_VIEW
     218SEARCH_VIEW
     219TICKET_VIEW
    219220TIMELINE_VIEW
    220221WIKI_VIEW
    … …  
    223224//**authenticated**//
    224225{{{
    225 TICKET_CREATE
    226 TICKET_MODIFY
    227 WIKI_CREATE
    228 WIKI_MODIFY 
    229 }}}
     226TICKET_CREATE
     227TICKET_MODIFY
     228WIKI_CREATE
     229WIKI_MODIFY
     230}}}
     231
    230232----
    231233See also: TracAdmin, TracFineGrainedPermissions