View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008753 | 10000-003: Address Space | Spec | public | 2023-03-23 12:19 | 2024-05-14 15:23 |
| Reporter | Matthias Damm | Assigned To | Jeff Harding | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.02 | ||||
| Fixed in Version | 1.05.04 RC1 | ||||
| Summary | 0008753: Use of AuditEvents for non-OPC UA actions | ||||
| Description | The AuditEvents section in Part 3 talks about actions initiated by a client to the server. With the rest of the text it looks like this can only be used for actions taken by an OPC UA Client to the OPC UA Server. But there could be other clients to a server / system that make relevant changes to the system. Could be an internal trigger, could be local HMI not connected through OPC UA. I think it makes sense to use AuditEvents also for such actions to get a full audit log. | ||||
| Tags | No tags attached. | ||||
| Commit Version | 1.05.04 RC | ||||
| Fix Due Date | 2023-11-07 | ||||
|
|
Added a clarification that vendor specific events may result in AuditEvent in addition to UA Client actions. |
|
|
Agreed to changes in Web Meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-03-23 12:19 | Matthias Damm | New Issue | |
| 2023-03-23 14:13 | Jim Luth | Assigned To | => Jeff Harding |
| 2023-03-23 14:13 | Jim Luth | Status | new => assigned |
| 2023-07-25 16:46 | Jim Luth | Commit Version | => 1.05.04 RC |
| 2023-07-25 16:46 | Jim Luth | Fix Due Date | => 2023-11-07 |
| 2024-05-07 15:26 | Jeff Harding | Status | assigned => resolved |
| 2024-05-07 15:26 | Jeff Harding | Resolution | open => fixed |
| 2024-05-07 15:26 | Jeff Harding | Fixed in Version | => 1.05.04 RC1 |
| 2024-05-07 15:26 | Jeff Harding | Note Added: 0021164 | |
| 2024-05-14 15:23 | Jim Luth | Status | resolved => closed |
| 2024-05-14 15:23 | Jim Luth | Note Added: 0021197 |
