Authenticating third-party services using Supabase Auth
Hi, I'm currently planning out to move my authentication from Firebase over to Supabase for my Flutter Project, but I have some concerns.
For one, I don't want to use Supabase Storage for instance, and opt to use AWS S3 instead (Not sure on this one yet).
Most importantly, I plan to host my own No-SQL database alongside Supabase for simple high-volume data on a VPS with a custom Auth API to validate Supabase authentications, but I'm kind of stumped on how to go about this, because this is the first time I'm working with multi-service infrastructure to fit my needs...
The main reasons for this kind of seperation is to minimize costs, and to keep my application as scalable, as possible.
But theres a few caviats to that approach:
- For every read and write, I need to make sure that the user is actually allowed to access this information.
- I currently use Firebase to store messages aswell as conversation headers (with last message, timestamp, participants). I dont authenticate supabase users because I'm still prototyping my way to a functional app. I'm not sure whether conversation headers should be stored in supabase or my nosql database, or if it makes functionally no difference once i found a working solution
So the questions regarding my problems boil down to:
Are there any supabase (or supabase-agnostic) resources for this (validating foreign/self-written services using Supabase Auth)?
What are the implications this might have for my Cloud Supabase instances? Do I need to self-host to do that?
I saw the Supabase Auth page, but I mightve stumbled over the answer I need.
For one, I don't want to use Supabase Storage for instance, and opt to use AWS S3 instead (Not sure on this one yet).
Most importantly, I plan to host my own No-SQL database alongside Supabase for simple high-volume data on a VPS with a custom Auth API to validate Supabase authentications, but I'm kind of stumped on how to go about this, because this is the first time I'm working with multi-service infrastructure to fit my needs...
The main reasons for this kind of seperation is to minimize costs, and to keep my application as scalable, as possible.
But theres a few caviats to that approach:
- For every read and write, I need to make sure that the user is actually allowed to access this information.
- I currently use Firebase to store messages aswell as conversation headers (with last message, timestamp, participants). I dont authenticate supabase users because I'm still prototyping my way to a functional app. I'm not sure whether conversation headers should be stored in supabase or my nosql database, or if it makes functionally no difference once i found a working solution
So the questions regarding my problems boil down to:
Are there any supabase (or supabase-agnostic) resources for this (validating foreign/self-written services using Supabase Auth)?
What are the implications this might have for my Cloud Supabase instances? Do I need to self-host to do that?
I saw the Supabase Auth page, but I mightve stumbled over the answer I need.
