View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010272 | Taler | taler-harness | public | 2025-08-21 17:49 | 2025-08-21 17:49 |
| Reporter | sebasjm | Assigned To | sebasjm | ||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 1.1 | ||||
| Target Version | 1.1 | ||||
| Summary | 0010272: implement self provision tests | ||||
| Description | https://docs.taler.net/design-documents/067-merchant-self-provisioning.html A merchant doing an account’s registration should get an email/phone notification with the comfirmation code. The merchant account should be in created state and only after using the confirmation code the account can be activated. A merchant with an activated account can call “forgot password”. Merchant should get a notification with the confirmation code that can be used to call the endpoint to change the password. A new login the with new password needs to be tested. An user that makes an amount of request above the threshold should get 429 for “sign up” or “forgot password” endpoints. A merchant that doesn’t have an activated account may be able to set and change all the configuration. But backend won’t take any action with it (for example, it won’t check KYC status). It may be also possible to delete the instance. | ||||
| Tags | No tags attached. | ||||
