I always wanted to know the requests that had been sent to my Storage to know who could access the download API as my security purposes don't allow to access this API , And I hidded the endpoints as much as I could but by somehow a user who had access to read a storage bucket could know my the file ID and did the download API "Content download" I only do "View" in my Flutter App .
My Question is , is there a way to know which user downloads the file , by function maybe or anyway to register the Download API Requests manually as Audit logs don't give accurete resulsts about Storage Buckets . " all my buckets are protected by premissions of appwrite no public or "any" buckets , + only Anrdoid/Ios apps used with appwrite , no web which protected hardly by SSL Pinning with custom SSL so if someone find a way to get the File ID I want to know him by registering all Download API requests but I don't know how to do it correctly or from where to start simply as I can't modify or edit the open source Appwrite to do that . is there a more simple way to register all "Download API" Requests with the user ID or something with functions and events maybe , but I am not sure that events supports the requests that download the files?
Appwrite doesn't track that stuff nor does it fire an event for read.
You tightened to put something in front of Appwrite to capture all of the network traffic. Then, you can grab the cookie and figure out the user
any recommendations for 3rd party tool can do such thing ?
no sorry
Recommended threads
- SELF HOSTING ISSUE, DATA NOT MIGRATING T...
Hey, devs, I recently tried to migrate my cloud instance to a self hosted version but my data is not transferred fully only the table structure is transferred ...
- Files access permissions
Am I right in understanding that file access permissions have been disabled (or broken again), and that shared access can now only be organized via tokens? Or i...
- Clarification about `Content` in terms a...
Hello, I'm looking into using Appwrite's cloud storage and got a bit concerned about this part in the terms page: https://appwrite.io/terms#content > Our Serv...