You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#3654 introduced a protection mechanism to the FileUpload component (validation code) to make sure the uploads come from a trusted FileUpload component, rendered to current portalID and for the current user ID. This protection is good but it currently prevents superusers from uploading files to the default portal (ID = -1) for example, or to any portal different than the one where the FileUpload component was rendered to.
Specifically, this affects the Assets module in Evoq, where the FileUpload component is used to upload files to any portal visible to the user.
Steps to reproduce
These steps are specific to Evoq, but can apply to other scenarios as well:
Description of bug
#3654 introduced a protection mechanism to the FileUpload component (validation code) to make sure the uploads come from a trusted FileUpload component, rendered to current portalID and for the current user ID. This protection is good but it currently prevents superusers from uploading files to the default portal (ID = -1) for example, or to any portal different than the one where the FileUpload component was rendered to.
Specifically, this affects the Assets module in Evoq, where the FileUpload component is used to upload files to any portal visible to the user.
Steps to reproduce
These steps are specific to Evoq, but can apply to other scenarios as well:
Current behavior
"Bad Request" error message is returned.
Expected behavior
File should get uploaded without issues.
Screenshots
Error information
Affected version
Affected browser
The text was updated successfully, but these errors were encountered: