Changes between Version 10 and Version 11 of BluePrintAuthorization

Timestamp:

06/18/10 20:53:43 (14 years ago)

Author:

Fran Boon

Comment:

--

BluePrintAuthorization

@@ -31 +31 @@
 }}}
  * A Developer needs to be able to restrict access to a Function
-  * Decorator function - although it doesn't support OR (we could easily write our own function to do this, though)
+  * ~~Decorator function : @auth.requires_membership("Administrator")~~
+   * doesn't support OR (we could easily write our own function to do this, though)
  * A Developer needs to be able to restrict access to a resource
   * REST controller can be blocked via a Decorator
-  * Full security policy can be invoked, but this is painful (based on protected by default & granted, whereas we want open by default & restricted)/untested within S3 recently
+  * Full security policy can be invoked, but this is painful (based on protected by default & granted manually) & untested within S3 recently
   * We could check for what other functions can access data? Sync. Hard to maintain though.
-  * Need a new method. Do all accesses go via S3XRC? If not, then needs to be a DAL-level method! Use an auth_permission table like Web2Py 'full' for tables? Set within 000_config.py, along with modules?
+  * Need a new method: open by default & restricted manually
+   * Do all accesses go via S3XRC? If not, then needs to be a DAL-level method!
+   * Use an {{{auth_permission}}} table similar to Web2Py 'full' for tables?
+   * Set within {{{000_config.py))), along with module permisisons?
  * A Developer needs to be able to restrict access to a record
-  * Add 2 reusable multiple=True fields to each table which needs this: {{{reader_id}}} & {{{writer_id}}} combined as {{{permissions_id}}}
+  * Add 2 reusable {{{multiple=True}}} fields to each table which needs this: {{{reader_id}}} & {{{writer_id}}} combined as {{{permissions_id}}}
    * Full backward compatibility since they default to None
-  * reader_id check as a new API function
-   * combine with the deleted==True check?
+  * reader_id checked with a new API function
+   * combine with the {{{deleted==True}}} check?
     * makes it easier to then replace that check with an 'inactive' field which is a date instead of a boolean, so that records can be set to expire (as well as giving us easy access to know when a record was deleted)
    * Option 1: Do the check alongside deleted as part of a big JOIN