View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004119 | Taler | obsolete component | public | 2016-01-02 11:19 | 2016-02-13 13:18 |
| Reporter | Christian Grothoff | Assigned To | Marcello Stanisci | 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 | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | 0.0 | ||||
| Target Version | 0.0 | ||||
| Summary | 0004119: integrate pin/tan authorization example | ||||
| Description | Right now, after the wallet we immediately jump to the 'success' page. In practice, the pin/tan should be queried after the mint has been selected. We should introduce such an 'authorization' page, i.e. where the user has so "solve" some arithmetic (42 * 499 / 3) to proceed. | ||||
| Tags | No tags attached. | ||||
| Is the wallet that does the form submission on the bank's DOM. So this control (the TAN thing) is only doable *before* the mint is chosen (the dialog through which a mint is chosen lives inside the wallet as well). In other words, once the user clicks on 'choose mint' the control never comes back to the bank's page. Doing the TAN control before choosing the mint doesn't seem to make things worse, and is quicker to implement. Other suggestions? | |
| If you do the TAN before choosing the mint, you cannot use the TAN to protect the destination (SEPA) account, which is exactly what modern TANs are supposed to do. So it has to be done afterwards, which is why this is an interesting feature to consider: basically, we do need to change this so that control does go back to the bank. => We should probably discuss this more in person. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-01-02 11:19 | Christian Grothoff | New Issue | |
| 2016-01-15 16:48 | Florian Dold | Assigned To | => Marcello Stanisci |
| 2016-01-15 16:48 | Florian Dold | Status | new => assigned |
| 2016-01-22 13:09 | Marcello Stanisci | Note Added: 0010079 | |
| 2016-01-22 22:18 | Christian Grothoff | Target Version | => 0.2 |
| 2016-01-22 22:47 | Christian Grothoff | Note Added: 0010086 | |
| 2016-02-08 17:58 | Marcello Stanisci | Status | assigned => informing |
| 2016-02-08 17:58 | Marcello Stanisci | Resolution | open => fixed |
| 2016-02-09 00:51 | Christian Grothoff | Status | informing => closed |
| 2016-02-13 13:18 | Christian Grothoff | Target Version | 0.2 => 0.0 |
| 2022-08-23 18:26 | Christian Grothoff | Category | bank (demonstrator) => py bank (demonstrator, obsolete) |
| 2023-12-03 00:23 | Christian Grothoff | Category | py bank (demonstrator, obsolete) => obsolete componet |
| 2023-12-11 19:08 | Florian Dold | Category | obsolete componet => obsolete component |