View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011174 | Taler | merchant backoffice SPA | public | 2026-03-03 17:46 | 2026-03-03 17:46 |
| Reporter | vecirex | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0011174: User must have possibility to have MFA codes resent | ||||
| Description | In the currently released taler-merchant package (v1.4.11), MFA codes are automatically sent, first to SMS, then to email. This is intended and good, but: In case a code doesn't arrive, it must be possible to require the code again. 1. A design document on the workflow should be created, also deciding if it's email or SMS first to be sent; in practice it's SMS, in an internal discussion email was said to be first. To be decided, in any case. 2. As for the workflow (suggestion): - Send the code as it's being done now - Additionally: Show an attention-grabbing countdown of 30 seconds alongside with a non-yet clickable button, allowing the user to check for the code, wait also a bit (bc of SMS gateway issues or spam filtering at any site in between the email delivery process) - As the countdown reaches zero, make the resend button clickable to have the code sent (functionality already exists from past versions, where it was actually always required to click to receive a code) | ||||
| Additional Information | I would say prio is high on this, as this can lead to issues in production otherwise, if there's a glitch in the networking or the involved services. Also it can happen that a spam filtering service notices that a user really wants to get a message, and lets the almost identical message just seen recently (seconds or minutes ago) through a second time. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-03-03 17:46 | vecirex | New Issue |
