View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008624 | Taler | libeufin-bank-ui (SPA) | public | 2024-03-10 13:48 | 2024-04-08 23:05 |
Reporter | Christian Grothoff | Assigned To | sebasjm | ||
Priority | high | Severity | feature | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
Product Version | git (master) | ||||
Target Version | post-1.0 | ||||
Summary | 0008624: need account setup meta-SPA | ||||
Description | Currently, setting up accounts for each merchant in the libeufin-bank and the merchant backend requires too many manual steps. We want another meta-SPA to drive this account setup across both systems. It should: 1) Be configured with the bank and backend base URLs, or maybe just with the domain (e.g. demo.taler.net) and assert that the sub-domains are 'bank' and 'backend'. 2) User must login with *both* the admin bank password and the backend default instance token; 3) Have a single form with all required fields to do the following: a) create bank account (with default settings) in libeufin-bank; fiat IBAN, phone/e-mail should be optional fields; b) create instance (with default settings) in merchant backend c) it should NOT ask for passwords/tokens (always auto-generate secure ones) Specifically, we need to at least collect: - slug for the instance name and account name (both same!) - legal merchant name (receiver-name on bank accounts!) - summary text for the template describing category of goods sold - optional: fiat IBAN, phone, e-mail for 2-FA 4) With that data, it should a) create the bank account (debt-limit: 0) b) create the instance c) link the instance to the bank account, including setting revenue-api URL and credentials to access bank account d) create a "default" template where the user must (only) enter the amount; but fix currency to regional currency 5) It should afterwards show the login URLs and credentials for the libeufin-bank and the merchant-backend it created in a way suitable for printing and sending to the merchant (so either nice printable HTML, or directly a PDF) with clear instructions where to use which credential (especially the respective username/base URL to enter into the browser). | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-03-10 13:48 | Christian Grothoff | New Issue | |
2024-03-10 13:48 | Christian Grothoff | Status | new => assigned |
2024-03-10 13:48 | Christian Grothoff | Assigned To | => sebasjm |
2024-03-10 13:49 | Christian Grothoff | Summary | need another meta-SPA => need account setup meta-SPA |
2024-03-10 14:04 | Christian Grothoff | Relationship added | child of 0008476 |
2024-03-26 22:04 | sebasjm | Target Version | 0.10 => post-1.0 |
2024-03-26 22:04 | sebasjm | Note Added: 0022002 | |
2024-03-26 22:05 | sebasjm | Relationship added | related to 0008660 |
2024-04-08 23:05 | Christian Grothoff | Relationship deleted | child of 0008476 |