User Story #249 (new)
Opened 18 years ago
Last modified 18 years ago
System-Types as audit trail
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | GatherReqs |
| Component: | Security | Keywords: | sudo, audittrail |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Some system-types have Details and some do not (so-called "Global types") To unify the two (see #230), it may be sensible to have all system-types have Details, and use the fields as the sudo audit trail (see #231).
For example, when user A (a sysadmin) logs in, all the system-types which are created (Events, EventLogs, Experimenters, etc.) could be given details.owner.id equals to user A. Currently, user A could said these ownership values to whatever s/he chooses. This new functionality would require minimal changes to transientDetails and managedDetails in BasicSecuritySystem. (As of r820)
Change History (1)
comment:1 Changed 18 years ago by jmoore
- Milestone changed from 3.0-M3 to GatherReqs
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
