Actions
Bug #27246
open
Shared files API usage in technique editors needs better error handling
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I hate Rudder for that
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
127
Name check:
To do
Fix check:
To do
Regression:
No
Description
With an user with read-only rights, when opening the technique editors in the "Resources" tab, existing technique resources are displayed. But when opening the file manager with the "Manage resources" button, no file is displayed, and there is a network error with the 403 forbidden error in the browser :
{"action":"writeFileResource","result":"error","errorDetails":"User 'adminread' is not authorized to access API 'writeFileResource"}
even if the request is to list files :
{"action":"list","path":"/"}
There are several 403 errors when attempting to use the file manager (upload files), with a notification Error when updating file, details: Unknown error.
- The notification error messages in the Elm app could be improved
- The shared files API is an internal API (an old one), and needs to be migrated to zio-json anyway, so all the logic of access needs to be changed when in zio-json, this would be in 9.0 or higher versions
Updated by Clark ANDRIANASOLO about 23 hours ago
- Category set to Web - Technique editor
Actions