View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002470 | 10000-004: Services | public | 2013-05-02 19:33 | 2013-10-10 23:05 | |
Reporter | Assigned To | Matthias Damm | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.03 | ||||
Summary | 0002470: Bad_UserAccessDenied, can be applied as operation result for other services? | ||||
Description | CMPWG 5/2/2013: Currently, Bad_UserAccessDenied is a service result, except for TransferSubscriptions (see Mantis 0633). According to its description: User does not have permission to perform the requested operation We have a test-case involving HistoryUpdate where we want to modify the history for a node that shows as read/write, but the current-user is read-only. In this case we would like to use "Bad_UserAccessDenied" but the spec shows "Bad_NotWritable". Can Bad_UserAccessDenied be used as an operation result in service calls other than TransferSubscriptions? | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Agreed that we should add Bad_UserAccessDenied to this service call. |
|
Added Bad_UserAccessDenied as operation level result for HistoryUpdate Resolved in document IEC 62541-4 - Services [Pre-CDV] 1.02.03.doc |
|
Agreed to in previous telecon |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-05-02 19:33 |
|
New Issue | |
2013-05-28 17:47 | Jim Luth | Status | new => assigned |
2013-05-28 17:47 | Jim Luth | Assigned To | => Matthias Damm |
2013-05-28 17:48 | Jim Luth | Note Added: 0004697 | |
2013-09-24 21:45 | Matthias Damm | Status | assigned => resolved |
2013-09-24 21:45 | Matthias Damm | Resolution | open => fixed |
2013-09-24 21:45 | Matthias Damm | Note Added: 0005004 | |
2013-10-10 23:05 | Jim Luth | Status | resolved => closed |
2013-10-10 23:05 | Jim Luth | Note Added: 0005058 | |
2013-10-10 23:05 | Jim Luth | Fixed in Version | => 1.03 |