View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004429 | Compliance Test Tool (CTT) Unified Architecture | 1 - Script Issue | public | 2018-10-30 18:47 | 2019-07-18 13:14 |
| Reporter | Alexander Allmendinger | Assigned To | Alexander Allmendinger | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.03.340.380 | ||||
| Target Version | 1.03 | Fixed in Version | 1.03.341.381 | ||
| Summary | 0004429: Security User Name Password \ 002 + 011: Using an insecure endpoint but connecting to a secure endpoint | ||||
| Description | Both scripts are working with an insecure endpoint description but then connecting to a secure endpoint. This works unless the definitions of UserIdentityToken differs between those two. In addition test case 002 should be skipped if the secure endpoint does explicitly define a security policy for this token. Because then we wouldn't execute this specific test case. | ||||
| Additional Information | Switch to the use of the secure endpoint | ||||
| Tags | No tags attached. | ||||
| Files Affected | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-10-30 18:47 | Alexander Allmendinger | New Issue | |
| 2018-10-30 18:47 | Alexander Allmendinger | Status | new => assigned |
| 2018-10-30 18:47 | Alexander Allmendinger | Assigned To | => Alexander Allmendinger |
| 2018-10-30 18:47 | Alexander Allmendinger | Note Added: 0009505 | |
| 2018-10-30 18:47 | Alexander Allmendinger | Status | assigned => resolved |
| 2018-10-30 18:47 | Alexander Allmendinger | Fixed in Version | => 1.03.341.381 |
| 2018-10-30 18:47 | Alexander Allmendinger | Resolution | open => fixed |
| 2019-01-28 14:10 | Paul Hunkar | Category | Script Issue => 1 - Script Issue |
| 2019-07-18 13:14 | Paul Hunkar | Status | resolved => closed |
| 2019-07-18 13:14 | Paul Hunkar | Note Added: 0010516 |
