Changes between Version 33 and Version 34 of BluePrintAuthenticationAccess

Timestamp:

01/12/09 18:44:18 (14 years ago)

Author:

Fran Boon

Comment:

Roles updated to current

BluePrintAuthenticationAccess

@@ -44 +44 @@
  * we should probably support these by adding hooks into the [wiki:BluePrintREST RESTlike controller]
 
-User maintenance can be done via appadmin until we develop our own UI.[[BR]]
-
-DRAFT:
-
-We use {{{t2_group}}} table for Contact Lists information
-
-We use {{{s3_role}}} table for Security access
+We use {{{t2_group}}} table for Roles & {{{t2_membership}}} to show which roles a user has.
  * roles initialised in {{{_db.py}}}
+ * 1st user to register gets Administrator role
  * module writers need to add any required roles there
 
-Membership of roles is controlled via the Many-to-Many table: {{{s3_roleholder}}}
+We expose this as s3.roles so that it is accessible to Controllers & Views.[[BR]]
+e.g.
+ * {{{appadmin.py}}}
+ * {{{layout.html}}}
 
-T3 defines a simple {{{t2.is_admin}}} defined in {{{db.py}}}:
-{{{
-is_admin=(t2.logged_in and (not settings.administrator_emails or t2.person_email in settings.administrator_emails))
-t2.is_admin=is_admin
-}}}
- * Function components protected with: {{{if not is_admin: t2.redirect('index',flash=T('Not Authorised'))}}}
- * appadmin protected in the same way :)
+User maintenance can be done via appadmin until we develop our own UI:
+ * ConfigurationGuidelines#Roles
 
 === Links ===