Changes between Version 3 and Version 4 of UserAccess


Ignore:
Timestamp:
Apr 10, 2008, 12:05:50 PM (11 years ago)
Author:
Horst Meyerdierks
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserAccess

    v3 v4  
    88control mechanisms, which we try to keep in sync with each other.
    99
    10 There are four kinds of access levels that a user account (or the anonymous user)
     10There are five kinds of access levels that a user account (or the anonymous user)
    1111may have:
    1212
    13  1. Ticket access. This is a different name for read access, but "read access" does not
    14     quite hit the spot as this includes the permission to create and comment on tickets.
    15     This excludes read access to the svn repository.
    16  1. User access. This is the same as ticket access, but also includes read access to
    17     the svn repository.
    18  1. Developer access. This is a different name for read/write access. The permissions
     13 1. Read access. This is designed for anonymous read access. It allows only read access
     14    to the trac environment, not to the repository. Compared to the next level, ticket
     15    access, this level does not allow the creation or adding to tickets. There is a
     16    genuine problem allowing anonymous ticket creation or adding to, as this will eventually
     17    be used by spammers to put hyperlinks onto public web pages (the ticket).
     18 2. Ticket access. This is designed for the case where certain users (or anonymous users)
     19    should be able to make full use of the ticketing system, but should not have access
     20    to the repository.
     21 3. User access. This is the original minimum access level (other than no access). It allows
     22    to read the trac environment, to make full use of the ticketing system, and to read the
     23    repository.
     24 4. Developer access. This is a different name for read/write access. The permissions
    1925    are a superset of user access. This includes read/write access to the svn repository.
    20  1. Admin access, or TRAC_ADMIN permission. This gives full access to the trac environment,
     26 5. Admin access, or TRAC_ADMIN permission. This gives full access to the trac environment,
    2127    but no access at all to the svn repository (other than browsing it through the wiki).
    2228
    23 To make these access levels real, the permission groups "ticket", "user" and "developer" have been
     29To make these access levels real, the permission groups "reader", "ticket", "user"
     30and "developer" have been
    2431defined. There is also an hourly job on the system that translates this information into
    2532svn repository access permissions. This is done in case that an admin has changed access