Guidance needed for secure coordinated account/project deletion with Supabase Storage #53318
Replies: 3 comments 1 reply
|
One pattern that covers most of this, with the caveat that the privileged routes can't be fenced by policies: 1. Tombstone first. Add a Before launch, test it with two accounts and a large resumable upload started just before you hit delete, and confirm the object is gone after the sweep. |
|
Ordering carries most of the risk here, so I would split the three questions 1. Sequence. Treat deletion as a lifecycle with an explicit marker, not a
2. Gates for new writes. Two mechanisms that are easy to conflate:
3. In-flight uploads and orphans. Make completion, not upload start, the Staging checks that actually validate the design, each with an expected result: These are documented Postgres/PostgREST semantics; the staging checks are the |
|
On your point 2: yes, the drain window has to cover the longest-lived credential, so 24 hours for TUS, not the 2-hour signed URL window. The bigger gap is proof. Best-effort cleanup only becomes evidence when every path (user JWT, signed URL, TUS, service role, S3 key, direct DELETE) is tried after the tombstone and shown to either fail or be swept. If an independent written validation would help unblock your launch, that's the kind of review I do: I'd go through the design and a test plan for each path and send findings within 48 hours. |
Uh oh!
There was an error while loading. Please reload this page.
Hello Supabase team and community,
We're preparing a Flutter + Supabase application for launch and need guidance on safely coordinating project/account deletion across PostgreSQL, Auth and Storage.
Our security testing identified several challenges:
We have tested RLS, database triggers and cleanup orchestration, but haven't established an enforceable solution covering all relevant API paths.
Questions:
We are keeping production deployment blocked until the design is independently validated.
We also submitted support ticket SU-547888 and received an acknowledgment, but no technical guidance yet.
Thank you.
All reactions