View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009238 | Taler | sandcastle (containerized demo deployment) | public | 2024-10-01 11:20 | 2025-03-31 23:15 |
| Reporter | oec | Assigned To | oec | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 1.0 stretch goals | Fixed in Version | git (master) | ||
| Summary | 0009238: Provide merchant self-provisioning service on demo.taler.net | ||||
| Description | Currently, web-developers who want to integrate payment with Taler into their web-offering have to setup a full merchant backend for integration and -tests. This is a significant hindrance for adoption and experimentation for many developers. If the demo system would allow a simple mechanism to create a merchant instance, web-developers could much more quickly work on integration with Taler. I propose, in the sandcastle setup, an additional service that allows anonymous users to provision themselves an merchant instance on backend.demo.taler.net that they can use for payments and can control with the normal SPA. (This is right now not possible as only admin on the backend can do this). The new service should - be a single program running on the demo instance, listening on a local TCP port - be routed via the reverse-proxy under a path backend.demo.taler.net/... - have a simple form with all required fields for setting up a merchant instance, similar to the SPA - however, the merchant-id should be randomly chosen by the service and returned - it should report an error if a merchant-name is already in use Optional: - automatically create a bank-account for the merchant on bank.demo.taler.net, too - a cronjob on the backend can delete for instances that where created but not used within N hours/days - a cronjob on the backend can delete instances that haven't been in use for at least M days | ||||
| Tags | No tags attached. | ||||
|
|
The implementation for such a provisioning service is ready to be tested and deployed, code at https://git.taler.net/taler-merchant-demos.git/log/?h=dev/oec/provision https://git.taler.net/sandcastle-ng.git/log/?h=dev/oec/provision |
|
|
Changes b221169e22c8110ad3979d8526c13b54a9793a9e in sandcastle-ng and 459e40ee4a813c1716e7ffda33fd28b4acf6741f in taler-merchant-demos introduced the self-provisioning service. On local setups (with SANDCASTLE_OVERRIDE_NAME=taler.localhost) it now runs under http://taler.localhost:4321/provision |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-10-01 11:20 | oec | New Issue | |
| 2024-10-01 11:20 | oec | Status | new => assigned |
| 2024-10-01 11:20 | oec | Assigned To | => oec |
| 2024-10-02 14:33 | oec | Summary | Provide TOFU-style merchant instance creation on backend.demo.taler.net => Provide merchant self-provisioning service on demo.taler.net |
| 2024-10-02 14:33 | oec | Description Updated | |
| 2024-10-21 12:36 | oec | Note Added: 0023549 | |
| 2024-10-21 12:37 | oec | Assigned To | oec => Florian Dold |
| 2024-10-21 12:37 | oec | Priority | high => normal |
| 2025-02-17 12:57 | Christian Grothoff | Target Version | 1.0 => 1.0 stretch goals |
| 2025-03-24 15:01 | Florian Dold | Assigned To | Florian Dold => oec |
| 2025-03-31 23:15 | oec | Status | assigned => resolved |
| 2025-03-31 23:15 | oec | Resolution | open => fixed |
| 2025-03-31 23:15 | oec | Fixed in Version | => git (master) |
| 2025-03-31 23:15 | oec | Note Added: 0024360 |
