Task #225 (new)
Opened 18 years ago
Last modified 14 years ago
Gather all references to "root"/0L/"system"/"user" and internalize to SecuritySystem
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Security | Version: | 3.0-M3 |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
Several places in the code base make assumptions based on Experimenter id ( == 0L ==> root) or Experimenter name ( .equals( "root" ) ==> root ). These all need to be factored out and centralized.
See:
- MergeEventListener
- UpdateFilter
- data.vm
- ...
- and all security tests.
There will need to be a ClientSecuritySystem for client-side tests. Now handled by serializable Role
Change History (6)
comment:1 Changed 18 years ago by jmoore
comment:2 Changed 18 years ago by jmoore
This may require #234 (so that client tests, etc. can also do SecuritySystem.isAdmin(user))
comment:3 Changed 18 years ago by jmoore
- Keywords iteration4 added; iteration2 removed
Moving to after vacation.
comment:4 Changed 18 years ago by jmoore
- Keywords iteration5 added; iteration4 removed
During cleanup for #328 this can be taken care of (client side as well). Moving to iteration5
comment:5 Changed 18 years ago by jmoore
- Description modified (diff)
- Keywords story114 iteration5 removed
- Milestone changed from 3.0-M3 to Unscheduled
Roles and EventContext provided by #328 allow this to be completed. Work has actually already begun, but priority of going through the code base and actually finding them has dropped.
data.vm and Roles (unless a workaround for data.vm can be found) should be the only locations where this information is encoded.
comment:6 Changed 14 years ago by jmoore
Note work on #1434
r787 introduces several get<Entity>[Id|Name] methods. Use these where possible. All stranded references to 0L and similar can now be ported.