Changes between Version 66 and Version 67 of BluePrintAuthenticationAccess


Ignore:
Timestamp:
06/18/10 09:27:28 (11 years ago)
Author:
Fran Boon
Comment:

Link to new BluePrintAuthorisation

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintAuthenticationAccess

    v66 v67  
    2727== Authorization ==
    2828We want to be able to provide a simple way of setting the overall security policy - allowing for flexible deployment options.
     29
     30New BluePrintAuthorisation.
     31
    2932 * Anonymous access is granted for all Read operations, with Create/Update/Delete requiring a user to be Authenticated
    3033 * Anonymous access isn't granted for anything - all access requires a user to be Authenticated
     
    4649(NB The Vol module currently uses a separate method)
    4750
    48 We also want to look at whether we should link the {{{auth_user}}} table with the [BluePrintPersonRegistry Person Registry]'s person table
     51We link the {{{auth_user}}} table with the [BluePrintPersonRegistry Person Registry]'s {{{pr_person}}} table.
    4952
    50 The admin role is pre-defined during initialisation in {{{00_db.py}}} (The first user to register will have this role by default):
     53The admin role is pre-defined during initialisation in {{{zzz_1st_run.py}}} (The first user to register will have this role by default):
    5154{{{
    52 table = 'auth_group'
     55table = "auth_group"
    5356# 1st-run initialisation
    54 if not len(db().select(db[table].ALL)):
    55     auth.add_group('Administrator',description='System Administrator - can access & make changes to any data')
     57if not len(db().select(db[table].id)):
     58    auth.add_group("Administrator", description="System Administrator - can access & make changes to any data")
    5659    # 1st person created will be System Administrator (can be changed later)
    57     auth.add_membership(1,1)
     60    auth.add_membership(1, 1)
    5861}}}
    5962