Changes between Version 17 and Version 18 of BluePrintAuthenticationAccess

Timestamp:

01/09/09 08:06:45 (16 years ago)

Author:

Fran Boon

Comment:

--

BluePrintAuthenticationAccess

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