pg_net extension-owned table permissions blocking hosted deployment #52317
Replies: 2 comments
|
your reading is right. there's currently no supported per-project change to those queue grants or rls policies by default, if recovery is entirely database work, i'd schedule a database function directly with if the edge function is essential, i'd move the scheduled call to an external scheduler or worker that keeps its credential outside postgres and calls the function directly |
|
There's a middle option between moving the schedule outside Postgres and accepting the exposure: keep pg_cron, but make the queued credential worthless outside one call. The scheduling docs say any login role can read the key while it sits in
A leak then lets someone run your recovery job early, and nothing else. Your migration check will still flag the PUBLIC grants, since that part can't change, but the risk goes from "credential in the queue" to "can trigger one idempotent job". |
Uh oh!
There was an error while loading. Please reload this page.
Hello Supabase team,
I'm developing a multiplayer application on a Free Supabase project and have encountered a permissions limitation while deploying its server-authoritative recovery worker.
Project reference:
sgewoxwnwbuphkwlqbadThe tables
net.http_request_queueandnet._http_responseare owned bysupabase_admin. Our migration correctly stops because theanonandauthenticatedroles inherit access throughPUBLIC.I found your documentation explaining that these grants cannot currently be changed on individual hosted projects.
Could you please confirm:
We do not want to bypass the security checks or weaken the authorization model.
Thank you.
Bug report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Additional context
Add any other context about the problem here.
All reactions