View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010025 | Taler | merchant backend | public | 2025-05-26 17:24 | 2025-10-31 19:49 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | tweak | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0 | ||||
| Target Version | 1.1 | Fixed in Version | 1.1 | ||
| Summary | 0010025: merchant backend blocks creation of admin instance when another instance has been created | ||||
| Description | It's currently/unexpectedly possible to create a non-admin instance before the admin instance has been configured. It's very difficult to get out of this situation, since taler-merchant-passwd doesn't work if the instance hasn't been created in the first place. Only option to fix this is to purge the instance and re-create everything. We should avoid getting into this in the first place, either by: (a) disallowing the creation of a non-admin instance before the admin instance has been configured (b) still allowing the admin instance to be created if other instances have been created | ||||
| Tags | ux | ||||
| Eh, that was actually seen as a feature: create a non-admin instance to enforce single-instance use, or delete your admin account to lock down a system and prevent direct interference with instances via the admin account. Maybe we should document this more, but I consider this not a bad feature to have! | |
| Problem is: This is a state that we can't recover from. It IMO should always be possible to change easily the admin credentials when you have root on the server. => As discussed offline, taler-merchant-passwd should simply create a (dummy, unconfigured) admin instance so that the admin password can be set. | |
| Fix committed to master branch. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-26 17:24 | Florian Dold | New Issue | |
| 2025-05-27 07:03 | Christian Grothoff | Note Added: 0025016 | |
| 2025-05-27 07:03 | Christian Grothoff | Severity | minor => tweak |
| 2025-05-27 07:03 | Christian Grothoff | Status | new => acknowledged |
| 2025-05-27 07:03 | Christian Grothoff | Product Version | => 1.0 |
| 2025-05-27 07:03 | Christian Grothoff | Target Version | 1.0 stretch goals => post-1.0 |
| 2025-05-27 14:44 | Florian Dold | Note Added: 0025025 | |
| 2025-05-27 14:44 | Florian Dold | Assigned To | => Florian Dold |
| 2025-05-27 14:44 | Florian Dold | Status | acknowledged => assigned |
| 2025-06-04 22:22 | Christian Grothoff | Assigned To | Florian Dold => |
| 2025-06-04 22:22 | Christian Grothoff | Status | assigned => implementing |
| 2025-06-04 22:22 | Christian Grothoff | Tag Attached: ux | |
| 2025-10-23 10:53 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-10-23 10:53 | Christian Grothoff | Status | implementing => assigned |
| 2025-10-23 10:53 | Christian Grothoff | Status | assigned => implementing |
| 2025-10-23 15:02 | Christian Grothoff | ||
| 2025-10-23 15:02 | Christian Grothoff | Note Added: 0026236 | |
| 2025-10-23 15:02 | Christian Grothoff | Status | implementing => informing |
| 2025-10-23 15:02 | Christian Grothoff | Resolution | open => fixed |
| 2025-10-23 15:02 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-10-23 15:02 | Christian Grothoff | Target Version | post-1.0 => 1.2 |
| 2025-10-23 22:50 | Christian Grothoff | Fixed in Version | 1.2 => 1.1 |
| 2025-10-23 22:51 | Christian Grothoff | Target Version | 1.2 => 1.1 |
| 2025-10-31 19:49 | Christian Grothoff | Status | informing => closed |