I thought about it a little bit,
We initialize plugins before an user is logged in (because we need auth plugins to work to fetch and restore the connected user for exemple). But here you need the supabase sdk to be initialised after the user was logged in, so you want to make it login to a third party first. But you will probably have a hard time making the third party be the authentication provider for supabase then (Having a Xano token will not magically make you able to access your supabase resources, except if every supabase request is proxied by xano).
And as we cannot allow binding in the plugin settings easily so you will not be able to make it dynamically dependent of the user. Another issue is you cannot have multiple auth system in the same time so no Supabase Auth and Xano Auth.
But I’ve an idea,
I think the easiest flow would be to have
- A login screen where you enter the user email first
- A special endpoint (in xano or supabase or somewhere else) you can send the user email and it will return the supabase instance url and public key related to this user
- We should provide a new action allowing you to reconnect the supabase instance with the settings you received
- Once reconnected to the specific user instance, the user can finish his signin process by entering his password and it will execute the sign in action normally
It works only if the schema is exactly the same across all the instances of course.
@Broberto We are working on it right now. The idea is still to allow everyone to develop plugins (auth, datasource, extension), I don’t have any estimation to communicate as I don’t know if we will release it as soon as it’s ready