View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011107 | Taler | merchant backend | public | 2026-02-18 22:45 | 2026-02-18 22:47 |
| Reporter | vecirex | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0011107: Backend for sms auth needs fixing for cases where number wrong (e.g., too short, too long, or invalid (like flipped digit)) | ||||
| Description | Unfortunately, from our current scripts we get status codes like 400 or 404 for the two gateway providers we have, when we do like +41 79 NNN NN NN K, while K is too much +41 79 NNN NN N_, while an N is missing +41 79 NNN NN WN, with an W turning the number invalid | ||||
| Steps To Reproduce | Doing it wrong with a pattern above, the following happens (for both SMS auth providers, telesign and clicksend): curl: (22) The requested URL returned error: 400 telesign failed. Polling message status (message_id: 1F10D12F-2AFA-6988-9122-3549D9A5CD0D)... curl: (22) The requested URL returned error: 404 clicksend failed. All SMS providers failed. taler-merchant-httpd@1b0bd36dc346:/usr/local/bin$ | ||||
| Additional Information | Of course this will also happen if it's utterly wrong, like just "+41", which currently even the backoffice SPA lets through. | ||||
| Tags | No tags attached. | ||||
| related to | 0011106 | new | Phone numbers need proper checking |
