Changes between Version 8 and Version 9 of TracDev/Proposals/EvenFinerGrainedPermissions

Timestamp:

Mar 11, 2017, 10:55:37 PM (7 years ago)

Author:

Ryan J Ollos

Comment:

Point to another example.

TracDev/Proposals/EvenFinerGrainedPermissions

@@ -9 +9 @@
  - lack of precision over the '''target''' of the check (#8653)
 
-This has lead to put this additional precision in the permission action itself, for example:
+This has lead to proposed or actual changes that add precision in the permission action itself, for example:
  - user related:
    - TICKET_IS_OWNER in #7438
@@ -15 +15 @@
    - TICKET_EDIT_COMMENT in #454
    - TICKET_EDIT_DESCRIPTION in #8548
+   - TICKET_EDIT_MILESTONE in #8778
 
 IPermissionPolicy plugins have the same tendency.
@@ -31 +32 @@
 For extending the precision over the '''target''', we could have a very simple set of permissions (''read'', ''modify'', ''delete'', ''append'', for example) and use child resources to identify sub-elements of a resource (like fields or comments).
 
-For introducing more elaborate concepts about the '''user''', we could use virtual groups. In a similar way than  the ''authenticated'' group currently represents the sets of authenticated users, we could imagine group providers attributing special membership to an user, depending on which ''resource'' is being targeted. Therefore we could imagine an ''owner'' or ''author'' virtual groups (#7438).
+For introducing more elaborate concepts about the '''user''', we could use virtual groups. In a similar way than  the ''authenticated'' group currently represents the sets of authenticated users, we could imagine group providers attributing special membership to a user, depending on which ''resource'' is being targeted. Therefore we could imagine an ''owner'' or ''author'' virtual groups (#7438).
 
 == Performance