kangmingtay

re-installing the app will remove any locally persisted state - which includes the anonymous user’s sign in info

in a web app, we store this stare in either local storage / cookies

in a mobile app, this state is stored in the local storage equivalent - SharedPreferences for android and NSUserDefaults for IOS

supabase auth stores your users in the same database created, just in a separate schema so you have full access to it to perform joins or enforce referential integrity.

If you're using Flutter, we do have a chat app example that has a basic email + password login. (https://github.com/supabase-community/flutter-chat)

Actually, we are experimenting with a Terraform provider to manage a project configuration, starting with Auth.

What are some other things you'd like to see in the Terraform provider?

[1]: supabase-terraform (https://github.com/supabase-community/supabase-terraform)

Supabase Auth Engineer here. We initially started off with the SAML 2.0 protocol since it's the one of the oldest protocols and also one that's used by most enterprises. We're definitely looking to add OIDC based SSO support soon so stay tuned!

Hi, Supabase Auth Engineer here. Interesting, just wondering if there's a reason behind choosing to roll your own iDP instead of using one of the big ones out there (Okta, Azure, GSuite) ?

Hi, Supabase Auth Engineer here. Thanks for pointing this out, we'll update our blogpost to reflect this.

Hi, Supabase Auth Engineer here. We are very close to feature parity with Firebase Auth. Off the top of my head, the 2 features we're missing right now is anonymous authentication and multi-tenancy.

We're also gonna be launching something auth-related this week too so stay tuned!