| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011049 | Taler | libeufin-bank webui | public | 2026-02-11 08:32 | 2026-03-20 23:55 |
| Reporter | Antoine A | Assigned To | Antoine A | 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 | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.5 | Fixed in Version | 1.5 | ||
| Summary | 0011049: Login error are formatted as unexpected errors | ||||
| Description | See the screenshot for more details | ||||
| Tags | No tags attached. | ||||
| i changed the title, the description "wrong credentails" is in fact something correct based on the error code returned by the server. Based on the username you used a message "user not found" might be better but currently the server doesn't return a different code for that. image-2.png (11,462 bytes) | |
| 74c60e6f4 the title is better but no further change | |
| I think it would be better if libeufin return a different error code if the account is not found, otherwise this can be closed | |
| I think the error should be better integrated in the UI, it looks like an error that should never happens but it's something that we expect to happens. I think we should handle differently errors that a user should handle and one the admin/dev should handle | |
| For unhappy path there is only 3 types: 1) on the spec, like this one. The message is short and should explain very well what happens in the user language. Usually not a problem but the operation failed. 2) not in the spec, this are "unexpected" problems, it could be the 1) but it was not in the spec or one of the server/client has different interpretation of the spec and needs to be fixed. the app do the best to explain the error with all the information it have 3) bugs, breaks the app. can't continue. If you are saying that there should be even a lighter version that (1) I disagree, it should be simple and work. And i think if the description is short the message is not intrusive. In you screenshot the "debug info" is enable, if that is very intrusive this can be moved to the sidebar. This is not something a normal user will want so I guess in the sidebar is ok image-3.png (24,166 bytes) | |
| 21bf079c5..8e620b99a moving "show debug info" to a side bar and removing the persistent feature (which is only useful if you are a dev) now the app starts always with debug = false, even after reload | |