Changes between Version 10 and Version 11 of Modules/Auth

Timestamp:

2010-12-13T15:35:24+01:00 (14 years ago)

Author:

Erik Roos

Comment:

--

Modules/Auth

@@ -2 +2 @@
 == Requirements list ==
 === Authentication ===
+ * Forms of Authentication:
+  * Database (user-pass)
+  * OpenID
+  * IP-based
+  * LDAP-based + specific flavors like RUG and UMCG login
  * Registration of users includes email verification
  * Users should be able to login and logout
+ * Users should be able to change their passwords
 
 === Authorization ===
- * Resources are tables, rows, columns, files (for pipelines?)
+ * Resources are tables, rows, columns, query-sets (e.g. only the Lengths in rows where Length > 1.80m), files (for pipelines)
  * Subjects are users, groups, public users (unauthenticated) and exactly one administrator
- * Permissions include read, write, execute (for pipelines?) and ownership
- * Resources must have exactly one user with ownership rights
+ * Permissions include read, write (also implies delete), execute (for pipelines) and ownership
+ * Resources must have exactly one owner; this can either be a user or a group. The latter option is not preferable for us and needs to be set explicitly by the administrator.
  * Permissions are provided for resources x subjects
  * The administrator has all permissions excluding ownership on all resources
- * Authenticated users can request permissions for resources. Requests are sent to the user with ownership rights of the resource.
+ * Authenticated users can request permissions for resources. Requests are sent to the user or group with ownership rights of the resource.
  * Groups can be created by users who have write rights on the MolgenisGroup table. The administrator is the owner of the MolgenisGroup table and can delegate rights to other users.
  * In case of an UpdateDatabase all permissions are reset (except for administrator)
- * The public user has reading permissions on all resources
- * Administrator can pass on permissions from parent tables to child tables with a toggle button
+ * The public user has by default no reading permissions on any resource, unless explicitly set by the administrator.
+ * Administrator can pass on permissions from parent tables to child tables and between xref-linked tables with a toggle button
 
 === Example ===