View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006003 | Taler | exchange | public | 2019-12-22 12:04 | 2019-12-23 12:33 |
| Reporter | Marcello Stanisci | 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 | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0006003: must align bank-lib tests to new Python bank's password management interface | ||||
| Description | So far, bank-lib tests relied on known-in-advance passwords to login at the Python bank and perform operations like requesting histories or issuing wire transfers. Since the Python bank now generates random passwords for users that are programmatically created, the bank-lib tests cannot login anymore. And furthermore, the Python bank has only one *interactive* way to let users change their passwords, that makes a programmatic usage from tests more problematic. | ||||
| Additional Information | Logs showing the "401 Unauthorized" error: Dec 22 13:03:51-927695 test-bank-api-with-(fake)bank-new-26098 INFO Bank serves at `http://localhost:8081/' 2019-12-22 12:03:52,059 middleware ERROR Error: authentication failed, while serving /history?auth=basic&account_number=1&delta=1&direction=both&cancelled=omit&ordering=ascending Unauthorized: /history 2019-12-22 12:03:52,060 log WARNING Unauthorized: /history Dec 22 13:03:52-060245 test-bank-api-with-(fake)bank-new-26098 ERROR Unwanted response code from /history[-range]: 401 Dec 22 13:03:52-060283 test-bank-api-with-(fake)bank-new-26098 ERROR Failed at command `history-0' 22/Dec/2019:12:03:51 +0000 HTTP/1.1 GET /history?auth=basic&account_number=1&delta=1&direction=both&cancelled=omit&ordering=ascending HTTP/1.1 => 401 | ||||
| Tags | No tags attached. | ||||
| Oh, this is a big RC issue. Why was this changed? Can we have a way to get the old behavior, maybe with an additional command-line switch (--test-acounts) or something like that? | |
| Fixed in Git master by wrapping taler-bank-manage with taler-bank-manage-testing script that sets up the passwords as before -- using psql database hacking. Ugly, but Django doesn't allow non-interactive setting of passwords otherwise. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-12-22 12:04 | Marcello Stanisci | New Issue | |
| 2019-12-22 12:04 | Marcello Stanisci | Status | new => assigned |
| 2019-12-22 12:04 | Marcello Stanisci | Assigned To | => Christian Grothoff |
| 2019-12-22 12:04 | Marcello Stanisci | Assigned To | Christian Grothoff => |
| 2019-12-22 12:09 | Marcello Stanisci | Additional Information Updated | |
| 2019-12-22 12:10 | Christian Grothoff | Note Added: 0015206 | |
| 2019-12-22 12:11 | Christian Grothoff | Product Version | => git (master) |
| 2019-12-22 12:11 | Christian Grothoff | Target Version | => 0.6 |
| 2019-12-23 12:32 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2019-12-23 12:32 | Christian Grothoff | Status | assigned => informing |
| 2019-12-23 12:32 | Christian Grothoff | Resolution | open => fixed |
| 2019-12-23 12:32 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2019-12-23 12:32 | Christian Grothoff | Note Added: 0015213 | |
| 2019-12-23 12:33 | Christian Grothoff | Status | informing => closed |