Changes between Version 66 and Version 67 of BluePrintAuthenticationAccess

Timestamp:

06/18/10 09:27:28 (14 years ago)

Author:

Fran Boon

Comment:

Link to new BluePrintAuthorisation

BluePrintAuthenticationAccess

@@ -27 +27 @@
 == Authorization ==
 We want to be able to provide a simple way of setting the overall security policy - allowing for flexible deployment options.
+
+New BluePrintAuthorisation.
+
  * Anonymous access is granted for all Read operations, with Create/Update/Delete requiring a user to be Authenticated
  * Anonymous access isn't granted for anything - all access requires a user to be Authenticated
@@ -46 +49 @@
 (NB The Vol module currently uses a separate method)
 
-We also want to look at whether we should link the {{{auth_user}}} table with the [BluePrintPersonRegistry Person Registry]'s person table
+We link the {{{auth_user}}} table with the [BluePrintPersonRegistry Person Registry]'s {{{pr_person}}} table.
 
-The admin role is pre-defined during initialisation in {{{00_db.py}}} (The first user to register will have this role by default):
+The admin role is pre-defined during initialisation in {{{zzz_1st_run.py}}} (The first user to register will have this role by default):
 {{{
-table = 'auth_group'
+table = "auth_group"
 # 1st-run initialisation
-if not len(db().select(db[table].ALL)):
-    auth.add_group('Administrator',description='System Administrator - can access & make changes to any data')
+if not len(db().select(db[table].id)):
+    auth.add_group("Administrator", description="System Administrator - can access & make changes to any data")
     # 1st person created will be System Administrator (can be changed later)
-    auth.add_membership(1,1)
+    auth.add_membership(1, 1)
 }}}