Bienvenue sur

Bienvenue sur , le site de la communauté des utilisateurs francophones de PostGIS.

PostGIS ajoute le support d'objets géographique à la base de données PostgreSQL. En effet, PostGIS "spatialise" le serverur PostgreSQL, ce qui permet de l'utiliser comme une base de données SIG.

Maintenu à jour, en fonction de nos disponibilités et des diverses sorties des outils que nous testons, nous vous proposons l'ensemble de nos travaux publiés en langue française.

Changes between Initial Version and Version 1 of TracPermissions

21/09/2011 00:47:47 (11 years ago)



  • TracPermissions

    v1 v1  
     1= Trac Permissions = 
     4Trac uses a simple, case sensitive, permission system to control what users can and can't access. 
     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. 
     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. 
     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 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". 
     13== Graphical Admin Tab == 
     14''This feature is new in version 0.11.'' 
     16To access this tab, a user must have `TRAC_ADMIN privileges`. This can be performed as follows (more on the trac-admin script below): 
     18  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 
     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). 
     24An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [ AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user. 
     26== Available Privileges == 
     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. 
     30Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''): 
     32=== Repository Browser === 
     34|| `BROWSER_VIEW` || View directory listings in the [wiki:TracBrowser repository browser] || 
     35|| `LOG_VIEW` || View revision logs of files and directories in the [wiki:TracBrowser repository browser] || 
     36|| `FILE_VIEW` || View files in the [wiki:TracBrowser repository browser] || 
     37|| `CHANGESET_VIEW` || View [wiki:TracChangeset repository check-ins] || 
     39=== Ticket System === 
     41|| `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] || 
     42|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] || 
     43|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] || 
     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_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. || 
     50Attention: the "view tickets" button appears with the `REPORT_VIEW` permission. 
     52=== Roadmap === 
     54|| `MILESTONE_VIEW` || View milestones and assign tickets to milestones. || 
     55|| `MILESTONE_CREATE` || Create a new milestone || 
     56|| `MILESTONE_MODIFY` || Modify existing milestones || 
     57|| `MILESTONE_DELETE` || Delete milestones || 
     58|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions || 
     59|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] || 
     60|| `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN || 
     62=== Reports === 
     64|| `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. || 
     65|| `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] || 
     66|| `REPORT_CREATE` || Create new [wiki:TracReports reports] || 
     67|| `REPORT_MODIFY` || Modify existing [wiki:TracReports reports] || 
     68|| `REPORT_DELETE` || Delete [wiki:TracReports reports] || 
     69|| `REPORT_ADMIN` || All `REPORT_*` permissions || 
     71=== Wiki System === 
     73|| `WIKI_VIEW` || View existing [wiki:TracWiki wiki] pages || 
     74|| `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages || 
     75|| `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages || 
     76|| `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments || 
     77|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. || 
     79=== Permissions === 
     81|| `PERMISSION_GRANT` || add/grant a permission || 
     82|| `PERMISSION_REVOKE` || remove/revoke a permission || 
     83|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions || 
     86=== Others === 
     88|| `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page || 
     89|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries || 
     90|| `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 [trac:wiki:0.11/TracIni trac show_email_addresses configuration option is false] || 
     93== Granting Privileges == 
     95You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command: 
     97  $ trac-admin /path/to/projenv permission list 
     100This command will allow the user ''bob'' to delete reports: 
     102  $ trac-admin /path/to/projenv permission add bob REPORT_DELETE 
     105The `permission add` command also accepts multiple privilege names: 
     107  $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE 
     110Or add all privileges: 
     112  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN 
     115== Permission Groups == 
     117There are two built-in groups, "authenticated" and "anonymous". 
     118Any user who has not logged in is automatically in the "anonymous" group. 
     119Any user who has logged in is also in the "authenticated" group. 
     120The "authenticated" group inherits permissions from the "anonymous" group. 
     121For example, if the "anonymous" group has permission WIKI_MODIFY,  
     122it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well. 
     124Custom groups may be defined that inherit permissions from the two built-in groups. 
     126Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc. 
     128  $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN 
     129  $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN 
     130  $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY 
     131  $ trac-admin /path/to/projenv permission add bob developer 
     132  $ trac-admin /path/to/projenv permission add john developer 
     135Group 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'''. 
     137== Adding a New Group and Permissions == 
     138Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group. 
     140The 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) 
     142   $ trac-admin /path/to/projenv permission add bob beta_testers 
     143   $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN 
     147== Removing Permissions == 
     149Permissions can be removed using the 'remove' command. For example: 
     151This command will prevent the user ''bob'' from deleting reports: 
     153  $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE 
     156Just like `permission add`, this command accepts multiple privilege names. 
     158You can also remove all privileges for a specific user: 
     160  $ trac-admin /path/to/projenv permission remove bob '*' 
     163Or one privilege for all users: 
     165  $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN 
     168== Default Permissions == 
     170By 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. 
     171On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''. 
     175 BROWSER_VIEW  
     177 FILE_VIEW  
     178 LOG_VIEW  
     180 REPORT_SQL_VIEW  
     181 REPORT_VIEW  
     182 ROADMAP_VIEW  
     183 SEARCH_VIEW  
     184 TICKET_VIEW  
     186 WIKI_VIEW 
     191 TICKET_CREATE  
     192 TICKET_MODIFY  
     193 WIKI_CREATE  
     194 WIKI_MODIFY   
     197See also: TracAdmin, TracGuide and TracFineGrainedPermissions