View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002380 | 10000-004: Services | public | 2013-02-19 10:23 | 2013-08-20 20:40 | |
Reporter | Christian Zugfil | Assigned To | Matthias Damm | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.02 | ||||
Fixed in Version | 1.03 | ||||
Summary | 0002380: Clarify expected behavior if client sends empty user identity token | ||||
Description | It is unclear how a server should respond to an "empty" or user identity token. Is it allowed to use anonymous login as default or should the server return BadUserIdentityTokenInvalid? Both behaviors can be observed in current implementations. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Agreed to fix this by stating in the spec and in a 1.02 ERRATA: |
|
Added clarification to ActivateSession -> userIdentityToken |
|
agreed to text change. |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-02-19 10:23 | Christian Zugfil | New Issue | |
2013-02-19 17:58 | Jim Luth | Status | new => assigned |
2013-02-19 17:58 | Jim Luth | Assigned To | => Matthias Damm |
2013-02-19 17:59 | Jim Luth | Note Added: 0004472 | |
2013-02-19 18:00 | Jim Luth | Note Edited: 0004472 | |
2013-08-20 16:09 | Matthias Damm | Status | assigned => resolved |
2013-08-20 16:09 | Matthias Damm | Resolution | open => fixed |
2013-08-20 16:09 | Matthias Damm | Note Added: 0004936 | |
2013-08-20 20:40 | Jim Luth | Status | resolved => closed |
2013-08-20 20:40 | Jim Luth | Note Added: 0004945 | |
2013-08-20 20:40 | Jim Luth | Fixed in Version | => 1.03 |