Changes between Version 17 and Version 18 of BluePrintAuthenticationAccess


Ignore:
Timestamp:
01/09/09 08:06:45 (13 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintAuthenticationAccess

    v17 v18  
    88
    99Anonymous access is currently granted for all Read operations, with Create/Update/Delete requiring a user to be Authenticated: {{{t2.logged_in}}}
    10 * T2 can extend this by protecting resources with {{{t2.have_membership()}}} (functional check) & {{{t2.have_access()}}} (record-level security)
    11 * we should probably support this by adding hooks into the [wiki:BluePrintREST RESTlike controller]
     10 * T2 can extend this by protecting resources with {{{t2.have_membership()}}} (functional check) & {{{t2.have_access()}}} (record-level security)
     11 * we should probably support this by adding hooks into the [wiki:BluePrintREST RESTlike controller]
    1212
    1313The system supports Self-Registration, which won't be appropriate for all deployment scenarios.[[BR]]
     
    2222We use {{{t2_group}}} table for Contact Lists information
    2323
    24 We use {{{s3_role}}} table for Security access[[BR]]
    25 - roles initialised in {{{_db.py}}}[[BR]]
    26 - module writers need to add any required roles there
     24We use {{{s3_role}}} table for Security access
     25 * roles initialised in {{{_db.py}}}
     26 * module writers need to add any required roles there
    2727
    2828Membership of roles is controlled via the Many-to-Many table: {{{s3_roleholder}}}