View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009479 | Taler | merchant backoffice SPA | public | 2025-01-27 09:19 | 2025-04-30 20:51 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | normal | Severity | block | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009479: cannot add Taler Revenue API for latest libeufin-bank (regional currency setup/Netzbon) | ||||
| Description | The merchant backend SPA correctly (!) supports giving a username/password for auth type "with password", but then tries to access the taler-revenue API directly using that password. However (unless in compatibility mode), libeufin *requires* token authentication for that endpoint. Thus, what the SPA *must* do is use the /token endpoint to convert the username/password into a token and it should then internally also only persist the token (without expiration). Naturally, the type of token requested should just be a "revenue" token. Now, the endpoint URL for the /token API isn't part of the revenue API, but part of the core bank API (https://docs.taler.net/core/api-corebank.html#authentication), so I guess we should *first* ask about the authentication type, and then ask for the core bank API endpoint *if* the user picks "with password" and ask for the revenue API endpoint if there is token. | ||||
| Tags | No tags attached. | ||||
| related to | 0009523 | confirmed | Allow connecting the merchant backend to the bank revenue API via token in URI |
|
|
it's not clear if we want to support this flow > entering the login credentials of service A in service B is not a good pattern that we want to teach to users |
|
|
Well, then we should remove that option in the UI! I can live with that, too. But we shouldn't keep a mode where we store the full-access login credentials in the merchant backend... |
|
|
ACK, hidding the auth with token option under dev-view in merchant ui since there is no way to get that from the bank ui... unless you have dev knowledge. |
|
|
4bb0784c0..bb7a207f8 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-01-27 09:19 | Christian Grothoff | New Issue | |
| 2025-01-27 09:19 | Christian Grothoff | Status | new => assigned |
| 2025-01-27 09:19 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-01-27 09:20 | Christian Grothoff | Priority | urgent => normal |
| 2025-01-27 09:20 | Christian Grothoff | Target Version | 1.0 => 1.0 stretch goals |
| 2025-04-07 18:24 | sebasjm | Assigned To | sebasjm => Florian Dold |
| 2025-04-07 18:24 | sebasjm | Status | assigned => feedback |
| 2025-04-07 18:24 | sebasjm | Note Added: 0024430 | |
| 2025-04-26 02:15 | Florian Dold | Assigned To | Florian Dold => |
| 2025-04-28 07:34 | Christian Grothoff | Note Added: 0024694 | |
| 2025-04-28 07:34 | Christian Grothoff | Status | feedback => new |
| 2025-04-28 07:34 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-04-28 07:34 | Christian Grothoff | Status | new => assigned |
| 2025-04-28 08:47 | Christian Grothoff | Relationship added | related to 0009523 |
| 2025-04-30 19:46 | sebasjm | Note Added: 0024719 | |
| 2025-04-30 20:48 | sebasjm | Note Added: 0024729 | |
| 2025-04-30 20:48 | sebasjm | Status | assigned => resolved |
| 2025-04-30 20:48 | sebasjm | Resolution | open => fixed |
| 2025-04-30 20:51 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-04-30 20:51 | Christian Grothoff | Target Version | 1.0 stretch goals => 1.0 |
