2
Feature request: Disable all write access to the database by client (API/functions/storage/etc.)
Source: supabase/supabase#11129 · opened by @bennettdams
Feature request Is your feature request related to a problem? Please describe. I'm looking for a way to prevent any writes happening by the client as an anon user AND an authenticated user. I'm using Next.js & Prisma with Supabase for the database, auth and storage. I do all my changes via Next.js API endpoints, no writes are happening via the client e.g. in the browser. In these API endpoints I check for authentication or even if that user is allowed to execute the edit he wanted to. Describe the solution you'd like Right now, I don't think there's a way to disable all writes from the client. Only I (the code in my API) should be allowed to make any writes. So wherever I execute writes to the database (via Prisma), which is mostly API endpoints. The exception are writes to the storage, where inside an API endpoint I e.g. upload a file on behalf of the user, something like: Describe alternatives you've considered I fo…
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow direct access to database from edge functions
1 vote · 0 comments
Add Storage Backups in Sync with Database Backups
4 votes · 0 comments
Add Storage Adapter For Chrome.Local.Storage Api
3 votes · 0 comments
# Proposal: Virtual Storage Columns (Seamless DB-to-Storage Mapping)
1 vote · 0 comments
Add option to `supabase functions deploy` to delete non-local functions
2 votes · 0 comments
No comments yet.