View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007239 | Taler | exchange | public | 2022-05-07 17:10 | 2024-01-12 13:05 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.9 | Fixed in Version | 0.9 | ||
| Summary | 0007239: adding auditor does not trigger /keys update? | ||||
| Description | It *seemed* to me that after adding an auditor to an exchange deployment /keys is not immediately updated by the exchange to reflect the change. Might want to double-check that... | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-05-07 17:10 | Christian Grothoff | New Issue | |
| 2022-05-07 17:10 | Christian Grothoff | Status | new => assigned |
| 2022-05-07 17:10 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2022-06-05 18:59 | Christian Grothoff | Status | assigned => informing |
| 2022-06-05 18:59 | Christian Grothoff | Resolution | open => no change required |
| 2022-06-05 18:59 | Christian Grothoff | Fixed in Version | => 0.9 |
| 2022-06-05 18:59 | Christian Grothoff | Note Added: 0018919 | |
| 2022-06-05 18:59 | Christian Grothoff | Target Version | => 0.9 |
| 2022-11-04 19:53 | Christian Grothoff | Status | informing => closed |
| 2024-01-12 13:05 | Christian Grothoff | Category | exchange API (C) => exchange |