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
I'm using the User-Restricted Resource Access feature by setting the AUTH_FIELD setting. I've also enabled the media endpoint for files uploaded as part of one of my apps endpoints.
But I noticed that users have access to each others files when using the media endpoint. (They can't access the resource the file is connected to because that endpoint is respecting the AUTH_FIELD setting).
I'd like for users only to be able to access media linked to resources they have access to. Is it feasible/desirable that this should be a part of Eve? If not does anyone have any advice how I could implement something myself to do this using the hook system or a custom Flask route maybe?
The text was updated successfully, but these errors were encountered:
I just raised a new issue on this (trying to raise more attention as i think this is a fairly big issue). Thinking about it, maybe it is possible to do a pre-check:
look up the associated resource entry for the media resource being asked for
look up the user_id associated with the resource
run authentication test on that user_id and pass/fail the request (don't know if that is possible or not).
I'm using the User-Restricted Resource Access feature by setting the AUTH_FIELD setting. I've also enabled the media endpoint for files uploaded as part of one of my apps endpoints.
But I noticed that users have access to each others files when using the media endpoint. (They can't access the resource the file is connected to because that endpoint is respecting the AUTH_FIELD setting).
I'd like for users only to be able to access media linked to resources they have access to. Is it feasible/desirable that this should be a part of Eve? If not does anyone have any advice how I could implement something myself to do this using the hook system or a custom Flask route maybe?
The text was updated successfully, but these errors were encountered: