Changes between Version 53 and Version 54 of BluePrintAuthenticationAccess

Timestamp:

05/11/09 10:46:16 (16 years ago)

Author:

Fran Boon

Comment:

Authorization implementation

BluePrintAuthenticationAccess

@@ -58 +58 @@
  * DeveloperGuidelinesAuthenticationAccess
 
-There are 2 modes for Authorisation right now:[[BR]]
- * simple: Anonymous access is currently granted for all Read operations, with Create/Update/Delete requiring a user to be Authenticated
- * full: Uses Web2Py's Role-Based Access Control for table-level control (can be separated for C/R/U/D)
- * Record-level security to be integrated: http://groups.google.com/group/web2py/browse_thread/thread/e4b54f08ec6b66f9
+There are 3 modes for Authorisation right now:[[BR]]
+ * simple:
+  * Anonymous access is currently granted for all Read operations
+  * Create/Update/Delete requiring a user to be Authenticated
+ * table:
+  * Uses Web2Py's Role-Based Access Control for table-level control (can be separated for C/R/U/D)
+ * record:
+  * Uses Web2Py's Role-Based Access Control for record-level control (can be separated for C/R/U/D): http://groups.google.com/group/web2py/browse_thread/thread/e4b54f08ec6b66f9
 
-NB 'full' mode requires each permission to be explicitly granted, so we default to having all registered users as 'Readers' & only 'Administrators' being able to Create/Update/Delete. Administrators can manually add other users to 'Editors' if-required.[[BR]]
+NB 'table' & 'record' modes requires each permission to be explicitly granted.[[BR]]
+For 'table' mode, we default to having all registered users as 'Readers' & only 'Administrators' being able to Create/Update/Delete. Administrators can manually add other users to 'Editors' if-required.[[BR]]
 Modules can provide further restrictions in {{{models/zzz.py}}}
+
+'record' mode currently has no framework support to ease administration & hence isn't yet recommended.
 
 Whether a user is authorised or not is defined using {{{has_permission()}}} in {{{models/__db.py}}} & called by the [wiki:BluePrintREST RESTlike controller]
 
-We use {{{sahana_group}}} table for Roles & {{{sahana_membership}}} to show which roles a user has.
+We use {{{auth_group}}} table for Roles & {{{auth_membership}}} to show which roles a user has.
  * admin role initialised in {{{_db.py}}}
  * 1st user to register gets Administrator role