how does the security story look in supabase, spec...
# helpo
omri
05/26/2022, 7:16 PMhow does the security story look in supabase, specifically access control?
say i only plan on using the postgrest and realtime apis, is there a way to say "i only want the supabase-hosted backend to be able to connect to my db"?
because otherwise anyone who gets access to the correct credentials (they won't, but still) can access all of my data like they would on a regular postgres instance, no?
n
Needle
05/26/2022, 7:16 PMHello @omri!
This thread has been automatically created from your message in #843999948717555735 a few seconds ago.
We have already mentioned the @User so that they can see your message and help you as soon as possible!
Want to unsubscribe from this thread?
Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates.
Want to change the title?
Use the ``/title`` command!
We have solved your problem?
Click the button below to archive it.
o
omri
05/26/2022, 7:17 PMand stepping it up a notch: say i have a backend separate from my frontend (which as i've mentioned before only uses the postgrest and realtime apis), and the backend will use the regular postgres protocol, i'd like to allow it but only it (and supabase of course) to access the postgrest instance.
is that supported?
omri
05/26/2022, 7:23 PMthe access control story was one of the things that made us migrate away from heroku's postgres offering, since every developer added to the team (who has access to the heroku secrets which include the db credentials) adds another risk factor - what if they store the credentials locally to connect using some client and then their pc gets stolen?
you multiply this by the number of devs on the team and you get a royal headache.
rls does help secure things but not in this context.
s
silentworks
05/26/2022, 9:40 PMIn the context you are mentioning you would only be able to secure it that way by not inviting a member to the project which I think sort of defeats the purpose in a collaborative environment. I don't think any DB works in the manner you are asking about. If your laptop gets stolen and it has credentials on it, then that's already a compromise, you would just need to reset the DB password and go from there.
n
Needle
05/26/2022, 9:40 PMomri (2022-05-26)
s
silentworks
05/26/2022, 9:41 PMOr maybe I'm not understanding what you are asking here?
o
omri
05/27/2022, 2:03 AMI think you are
omri
05/27/2022, 2:04 AMWhat I've been told by a person who might become my supervisor of sorts at
$DAYJOBomri
05/27/2022, 2:06 AMHe was very displeased with the idea of me being able to just connect to our heroku postgres instance from my laptop (which was completely unencrypted so he did have a reason to worry, but I digress).
omri
05/27/2022, 2:06 AMAren't firewalls the solution for this?
omri
05/27/2022, 2:07 AMAlthough I can see how the needs of paas-style offerings might make having a persistent identifier for the actual physical machine that runs the code that connects to the db (which might not be necessary for something like a firewall, I'm not sure)