View Issue Details

IDProjectCategoryView StatusLast Update
0010272Talertaler-harnesspublic2025-09-10 15:13
Reportersebasjm Assigned Tosebasjm  
PriorityhighSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version1.1 
Target Version1.1 
Summary0010272: implement self provision tests
Descriptionhttps://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.

TagsNo tags attached.

Relationships

child of 0010224 confirmedFlorian Dold merchant backend self-provisioning [meta] [01sept] 

Activities

sebasjm

2025-09-09 15:17

developer   ~0025870

first test 62a2214cd..04e7e052d

sebasjm

2025-09-10 15:13

developer   ~0025877

04e7e052d..2c3931738

Issue History

Date Modified Username Field Change
2025-08-21 17:49 sebasjm New Issue
2025-08-21 17:49 sebasjm Status new => assigned
2025-08-21 17:49 sebasjm Assigned To => sebasjm
2025-08-31 19:18 Christian Grothoff Relationship added child of 0010224
2025-09-09 15:17 sebasjm Note Added: 0025870
2025-09-10 15:13 sebasjm Status assigned => resolved
2025-09-10 15:13 sebasjm Resolution open => fixed
2025-09-10 15:13 sebasjm Note Added: 0025877