| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010427 | Taler | merchant portal webui | public | 2025-09-19 11:32 | 2025-10-31 19:49 |
| Reporter | sebasjm | Assigned To | sebasjm | 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 | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0 | ||||
| Target Version | 1.1 | Fixed in Version | 1.1 | ||
| Summary | 0010427: better error details when the code is send too soon | ||||
| Description | > very weird error message > "A code was just sent. Please wait before requesting another one." > If possible, add countdown until possibility to request new code reported by vlada This requires more information from the backend, so I'm creating this issue in the backend first and checking with CG also. https://docs.taler.net/core/api-merchant.html#post-[-instances-$INSTANCE]-challenge-$CHALLENGE_ID IMO Instead of returning 204 No Content on the success we can return a duration and a hint: interface ChallengeStarted { // text that was sent with the code to identify between more than one message hint: string; // time until this challenge can be solved solve_expiration: Timestamp; // time while this tan channel is blocked for retry retry_expiration: Timestamp; } This information is not saved in SPA session and a reload (or using same account from another browser) can still get 429 Too many requests. It would be nice to have the same response so the SPA can render "you should already have one with hit xxx or you can try again at ... " | ||||
| Tags | No tags attached. | ||||
- Anonymous