View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008287 | Taler | libeufin (general) | public | 2024-01-30 13:03 | 2024-03-07 19:49 |
| Reporter | Antoine A | Assigned To | Antoine A | 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 | urgent | Severity | major | Reproducibility | N/A |
| Status | closed | Resolution | reopened | ||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0008287: Correction to the way we manage payto uris | ||||
| Description | In `libeufin`, all iban payto uris have their IBAN normalized (capitals without separator). In `libeufin-bank`, we use payto uris to identify accounts, to do this we have removed all the parameters from the URI query to get a canonical payto IBAN. But the "receiver-name" parameter is actually needed for other Taler components. For cashout payto that are shared with `libeufin-nexus`, we use a "full" IBAN uri, which is a canonical form with an "receiver-name" parameter. The receiver-name parameter is different from the legal name of the account. We must continue to identify accounts using payto uris and support several types of them (IBAN and x-taler-bank) while storing the receiver-name parameter. | ||||
| Tags | No tags attached. | ||||
| related to | 0007304 | closed | Christian Grothoff | should we normalize payto://-URIs in the exchange before hashing? [5d] |
| child of | 0008273 | closed | Florian Dold | package and upload libeufin 0.9.4 to ftp and stable Debian/Ubuntu server |
| I need to update the regional deployment script to set the payment method to x-taler-bank | |
| You might also find TALER_payto_normalize() in the exchange.git (src/util/payto.c) informative ;-). | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-30 13:03 | Antoine A | New Issue | |
| 2024-01-30 13:03 | Antoine A | Status | new => assigned |
| 2024-01-30 13:03 | Antoine A | Assigned To | => Antoine A |
| 2024-01-30 13:03 | Antoine A | Description Updated | |
| 2024-01-30 13:07 | Antoine A | Relationship added | related to 0007304 |
| 2024-02-02 20:17 | Antoine A | Status | assigned => informing |
| 2024-02-02 20:17 | Antoine A | Resolution | open => fixed |
| 2024-02-02 20:23 | Antoine A | Status | informing => feedback |
| 2024-02-02 20:23 | Antoine A | Resolution | fixed => reopened |
| 2024-02-02 20:23 | Antoine A | Note Added: 0021132 | |
| 2024-02-05 19:31 | Christian Grothoff | Relationship added | child of 0008273 |
| 2024-02-09 23:07 | Christian Grothoff | Note Added: 0021234 | |
| 2024-02-10 02:21 | Antoine A | Status | feedback => informing |
| 2024-02-10 22:31 | Christian Grothoff | Fixed in Version | => 0.9.4 |
| 2024-03-07 19:49 | Christian Grothoff | Status | informing => closed |