| 6 | | Permission privileges are managed using the [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin'' tab of the web interface. |
| 7 | | |
| 8 | | In 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. |
| 9 | | |
| 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 the privileges for will not be displayed in the navigation. |
| 11 | | 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". |
| | 6 | Permissions are managed using the [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin'' tab of the web interface. |
| | 7 | |
| | 8 | In 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. |
| | 9 | |
| | 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 privileges for will not be displayed in the navigation bar. |
| | 11 | 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//. |
| 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): |
| 16 | | {{{ |
| 17 | | $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN |
| 18 | | }}} |
| 19 | | |
| 20 | | Then, 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.''' |
| 21 | | |
| 22 | | 1. [[Image(htdocs:../common/guide/admin.png)]] |
| 23 | | 1. [[Image(htdocs:../common/guide/admin-permissions.png)]] |
| 24 | | 1. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]] |
| 25 | | |
| 26 | | An 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. |
| | 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 with a more detailed description [#GrantingPrivileges below]: |
| | 16 | {{{#!sh |
| | 17 | $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN |
| | 18 | }}} |
| | 19 | |
| | 20 | Then, 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.''' |
| | 21 | |
| | 22 | [[Image(htdocs:../common/guide/admin.png)]] |
| | 23 | |
| | 24 | [[Image(htdocs:../common/guide/admin-permissions.png)]] |
| | 25 | |
| | 26 | [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]] |
| 45 | | || `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] || |
| 46 | | || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || |
| 47 | | || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || |
| 48 | | || `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 || |
| 49 | | || `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. || |
| | 45 | || `TICKET_VIEW` || View existing [TracTickets tickets] and perform [TracQuery ticket queries] || |
| | 46 | || `TICKET_CREATE` || Create new [TracTickets tickets] || |
| | 47 | || `TICKET_APPEND` || Add comments and attachments to [TracTickets tickets], and edit description of ticket that the user created || |
| | 48 | || `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 || |
| | 49 | || `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. || |
| 94 | | || `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page || |
| 95 | | || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || |
| 96 | | || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins || |
| 97 | | || `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false || |
| | 92 | || `TIMELINE_VIEW` || View the [TracTimeline timeline] page || |
| | 93 | || `SEARCH_VIEW` || View and execute [TracSearch search] queries || |
| | 94 | || `CONFIG_VIEW` || Enables additional sections on ''About Trac'' that show the current configuration and the list of installed plugins || |
| | 95 | || `EMAIL_VIEW` || Shows email addresses even if [TracIni#trac-section trac show_email_addresses] configuration option is false || |
| | 96 | |
| | 97 | == Attachment Permissions |
| | 98 | |
| | 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 that the user possesses for that realm. |
| | 100 | |
| | 101 | The attachment actions are determined by the following permissions in the ticket, wiki and milestone realms: |
| | 102 | {{{#!table class="listing" |
| | 103 | ||= Granted By: =||= Ticket =||= Wiki =||= Milestone =|| |
| | 104 | || `ATTACHMENT_CREATE` || `TICKET_APPEND` || `WIKI_MODIFY` || `MILESTONE_MODIFY` || |
| | 105 | || `ATTACHMENT_VIEW` || `TICKET_VIEW` || `WIKI_VIEW` || `MILESTONE_VIEW` || |
| | 106 | || `ATTACHMENT_DELETE` || `TICKET_ADMIN` || `WIKI_DELETE` || `MILESTONE_DELETE` || |
| | 107 | }}} |
| | 108 | |
| | 109 | An authenticated user can delete an attachment //they added// without possessing the permission that grants `ATTACHMENT_DELETE`. |
| | 110 | |
| | 111 | If 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: |
| | 112 | {{{#!ini |
| | 113 | [extra-permissions] |
| | 114 | _perms = ATTACHMENT_CREATE, ATTACHMENT_DELETE, ATTACHMENT_VIEW |
| | 115 | }}} |
| | 116 | |
| | 117 | An alternative configuration adds an `ATTACHMENT_ADMIN` meta-permission that grants the other 3 permissions: |
| | 118 | {{{#!ini |
| | 119 | [extra-permissions] |
| | 120 | ATTACHMENT_ADMIN = ATTACHMENT_CREATE, ATTACHMENT_DELETE, ATTACHMENT_VIEW |
| | 121 | }}} |
| | 122 | |
| | 123 | The 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. |
| | 124 | |
| | 125 | == Granting Privileges |
| | 126 | |
| | 127 | Privileges are granted to users through [TracAdmin trac-admin]. The current set of privileges can be listed with the following command: |
| | 128 | {{{#!sh |
| | 129 | $ trac-admin /path/to/projenv permission list |
| | 130 | }}} |
| | 131 | |
| | 132 | This command will allow the user ''bob'' to delete reports: |
| | 133 | {{{#!sh |
| | 134 | $ trac-admin /path/to/projenv permission add bob REPORT_DELETE |
| | 135 | }}} |
| | 136 | |
| | 137 | The `permission add` command also accepts multiple privilege names: |
| | 138 | {{{#!sh |
| | 139 | $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE |
| | 140 | }}} |
| | 141 | |
| | 142 | Or add all privileges: |
| | 143 | {{{#!sh |
| | 144 | $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN |
| | 145 | }}} |
| | 146 | |
| | 147 | == Permission Groups |
| | 148 | |
| | 149 | There are two built-in groups, //authenticated// and //anonymous//. |
| | 150 | Any user who has not logged in is automatically in the //anonymous// group. |
| | 151 | Any user who has logged in is also in the //authenticated// group. |
| | 152 | The //authenticated// group inherits permissions from the //anonymous// group. |
| | 153 | For 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. |
| | 154 | |
| | 155 | Custom groups may be defined that inherit permissions from the two built-in groups. |
| | 156 | |
| | 157 | Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. |
| | 158 | {{{#!sh |
| | 159 | $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN |
| | 160 | $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN |
| | 161 | $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY |
| | 162 | $ trac-admin /path/to/projenv permission add bob developer |
| | 163 | $ trac-admin /path/to/projenv permission add john developer |
| | 164 | }}} |
| | 165 | |
| | 166 | Group 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'''. |
| | 167 | |
| | 168 | == Adding a New Group and Permissions |
| | 169 | |
| | 170 | Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. |
| | 171 | |
| | 172 | 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. |
| | 173 | {{{#!sh |
| | 174 | $ trac-admin /path/to/projenv permission add bob beta_testers |
| | 175 | $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN |
| | 176 | }}} |
| | 177 | |
| | 178 | == Removing Permissions |
| | 179 | |
| | 180 | Permissions can be removed using the 'remove' command. |
| | 181 | |
| | 182 | This command will prevent the user ''bob'' from deleting reports: |
| | 183 | {{{#!sh |
| | 184 | $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE |
| | 185 | }}} |
| | 186 | |
| | 187 | Just like `permission add`, this command accepts multiple privilege names. |
| | 188 | |
| | 189 | You can also remove all privileges for a specific user: |
| | 190 | {{{#!sh |
| | 191 | $ trac-admin /path/to/projenv permission remove bob '*' |
| | 192 | }}} |
| | 193 | |
| | 194 | Or one privilege for all users: |
| | 195 | {{{#!sh |
| | 196 | $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN |
| | 197 | }}} |
| 112 | | $ trac-admin /path/to/projenv permission add bob REPORT_DELETE |
| 113 | | }}} |
| 114 | | |
| 115 | | The `permission add` command also accepts multiple privilege names: |
| 116 | | {{{ |
| 117 | | $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE |
| 118 | | }}} |
| 119 | | |
| 120 | | Or add all privileges: |
| 121 | | {{{ |
| 122 | | $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN |
| 123 | | }}} |
| 124 | | |
| 125 | | == Permission Groups |
| 126 | | |
| 127 | | There are two built-in groups, "authenticated" and "anonymous". |
| 128 | | Any user who has not logged in is automatically in the "anonymous" group. |
| 129 | | Any user who has logged in is also in the "authenticated" group. |
| 130 | | The "authenticated" group inherits permissions from the "anonymous" group. |
| 131 | | For example, if the "anonymous" group has permission WIKI_MODIFY, |
| 132 | | it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. |
| 133 | | |
| 134 | | Custom groups may be defined that inherit permissions from the two built-in groups. |
| 135 | | |
| 136 | | Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. |
| 137 | | {{{ |
| 138 | | $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN |
| 139 | | $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN |
| 140 | | $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY |
| 141 | | $ trac-admin /path/to/projenv permission add bob developer |
| 142 | | $ trac-admin /path/to/projenv permission add john developer |
| 143 | | }}} |
| 144 | | |
| 145 | | Group 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'''. |
| 146 | | |
| 147 | | == Adding a New Group and Permissions |
| 148 | | Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. |
| 149 | | |
| 150 | | 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) |
| 151 | | {{{ |
| 152 | | $ trac-admin /path/to/projenv permission add bob beta_testers |
| 153 | | $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN |
| 154 | | |
| 155 | | }}} |
| 156 | | |
| 157 | | == Removing Permissions |
| 158 | | |
| 159 | | Permissions can be removed using the 'remove' command. For example: |
| 160 | | |
| 161 | | This command will prevent the user ''bob'' from deleting reports: |
| 162 | | {{{ |
| 163 | | $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE |
| 164 | | }}} |
| 165 | | |
| 166 | | Just like `permission add`, this command accepts multiple privilege names. |
| 167 | | |
| 168 | | You can also remove all privileges for a specific user: |
| 169 | | {{{ |
| 170 | | $ trac-admin /path/to/projenv permission remove bob '*' |
| 171 | | }}} |
| 172 | | |
| 173 | | Or one privilege for all users: |
| 174 | | {{{ |
| 175 | | $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN |
| 176 | | }}} |
| 177 | | |
| 178 | | == Default Permissions |
| 179 | | |
| 180 | | 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. |
| 181 | | On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. |
| 182 | | |
| 183 | | '''anonymous''' |
| 184 | | {{{ |
| 185 | | BROWSER_VIEW |
| 186 | | CHANGESET_VIEW |
| 187 | | FILE_VIEW |
| 188 | | LOG_VIEW |
| 189 | | MILESTONE_VIEW |
| 190 | | REPORT_SQL_VIEW |
| 191 | | REPORT_VIEW |
| 192 | | ROADMAP_VIEW |
| 193 | | SEARCH_VIEW |
| 194 | | TICKET_VIEW |
| 195 | | TIMELINE_VIEW |
| 196 | | WIKI_VIEW |
| 197 | | }}} |
| 198 | | |
| 199 | | '''authenticated''' |
| 200 | | {{{ |
| 201 | | TICKET_CREATE |
| 202 | | TICKET_MODIFY |
| 203 | | WIKI_CREATE |
| 204 | | WIKI_MODIFY |
| 205 | | }}} |
| | 226 | TICKET_CREATE |
| | 227 | TICKET_MODIFY |
| | 228 | WIKI_CREATE |
| | 229 | WIKI_MODIFY |
| | 230 | }}} |
| | 231 | |
