Changes between Version 7 and Version 8 of AuthModule/UserStories
- Timestamp:
- 2011-01-22T09:27:03+01:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AuthModule/UserStories
v7 v8 1 1 = Authentication and Authorization module user stories = 2 3 Data: 4 * structural elements include entities (table), fields (columns), and user interface screens 5 * instance elements are the 'rows' or 'objects'. 6 7 Users: 8 * anonymous user: users who are not logged in 9 * authenticated user: users that have registered to the system 10 * adminstrator: special authenticated user who may manage overall permissions for the MOLGENIS app. 11 12 Permission: 13 * read permission: ability to view the data 14 * write permissions: ability to edit the data 15 * execute: ability to use data inside processing 16 * ownership: ability to add or remove data or set permissions 17 * sharing permissions: that is row-level security which is defined as defining permissions per data row/object. 18 2 19 [[TOC()]] 3 == As a user I want the module to have a set of permissions including read, write, execute and ownership. == 20 21 == As authenticated user I want to define data permissions including read, write, execute and ownership. == 4 22 Acceptance criteria: 5 23 * Please add! … … 8 26 * Extend Permission enum in DatabaseLogin to cover read, write, execute and ownership. 9 27 10 == As a user I want the module to have a set of entities including tables, columns, rows and screens. ==28 == As an administrator I want to set permissions on entities including entities, fields, rows and screens. == 11 29 Acceptance criteria: 12 30 * Please add! … … 16 34 * Create an interface Authorizable with fields owner: xref->!MolgenisUser, shareRead: xref->!MolgenisGroup, shareWrite: xref->!MolgenisGroup. 17 35 18 == As a user I want the module to have a structure containing users and groups. Users can be part of groups. Both can have permissions on entities. If multiple permissions apply to an entity the narrower ones override the broader ones. == 36 == As authenticated user I want to create my own groups of users and add permissions on users or groups. If multiple permissions apply the broader ones override the narrower ones. == 37 19 38 Acceptance criteria: 39 * I want to say that my friend Peter can see all my Protocols but not all my ObservedValue except those ObservedValue I marked as 'public'. 20 40 * Please add! 21 41 … … 25 45 * Create a table that contains !MolgenisElements and connects them with !MolgenisUser's and Permissions. 26 46 * Make Molgenis check permissions via central class. (To be refined.) 27 28 == As a user I want to be able to change permissions (grant, revoke) for the entities I own. The permissions are strictly limited to the entity. No information from linked entities will show up if permissions have not been given. ==29 Acceptance criteria:30 * Please add!31 32 Tickets:33 47 * Create a user interface to manage permissions for the entities owned by the user that is logged in. 34 48 35 49 == As an administrator I want to be able to manage users and groups. == 36 50 Acceptance criteria: 51 * 37 52 38 53 Tickets: … … 41 56 == As an administrator I want to have the possibility to forward permissions from an entity to others. == 42 57 Acceptance criteria: 58 * I want that I can automatically derive my permissions on 'Sample' from the sharing permissions that are set on Investigation 43 59 * Please add! 44 60 … … 46 62 * Create a function as part of the admin interface to forward permissions from an entity to others that are connected with it (xref, mref). 47 63 48 == As a publicuser I want to see all the entities I am entitled to see without logging in. ==64 == As a anonymous user I want to see all the entities I am entitled to see without logging in. == 49 65 Acceptance criteria: 50 66 * Please add!
