Looking for Advice on Migrating Flask-Login to Auth0 or Supabase

Tips & Tricks
,
1

Hi all.
Has anyone here successfully implemented authentication using Auth0 or Supabase? I’m currently using Flask-Login and email-validator with Sendgrid for login and signup, but I’m looking to offload that functionality to a third-party.
The migration process for me is a bit too complex, so if you have any experience, tips, or guides to share? :folded_hands:

1 Like
2

I have supabase running in my express.js app. I like it so far.

Unfortunately, I haven’t migrating auth providers before so can’t weigh in there.

1 Like
3

I have. Absolute NIGHTMARE. I’m on week 2 of trying to unfudge it. Do not recommend.

Figure out auth plan. Stick with auth plan. If you are going to change it, FORK. Git no bueno.

1 Like
4

Well this isn’t encouraging, Eric.

I was thinking of moving off Neon to Auth0. Still don’t recommend? :rofl:

1 Like
5

My AI Dev Kit is integrated with Supabase for auth and DB. It works well.

I mention DB, because DB and auth are separate entities in Supabase. So the app has to create and manage a row in my DB users table, in sync with the separate auth users table. This is key to being able to manage the logged-in user with additional fields from the DB table.

I also currently only use email for signup/login, and appreciate 3rd party sign in providers add some trickiness. So if you are only working on an MVP/early version, I would probably suggest sticking with email only for now.

I do not envy you wanting to migrate though. Like @realfunnyeric says, find an auth plan and stick with it. Auth is one of those beasts that should be a simple isolated module to replace, but often has its fingers in too many parts of your app. Untangling spaghetti :blush:

6

Ugh, I know. The pains of building your first app is you don’t think of these things. I pushed forward just leaving things as is because it’s going to be brutal making the move. I do want to switch for the users’ sake but man, it’s going to be a beast to move auth over.

1 Like
7

@adrianvonbausse and @shawn93…

  1. Replicate your app into a 2nd temporary version, so you don’t break your main app. Or have a rock solid plan for doing a rollback (including your DB schema).

  2. Stick it on High autonomy and Plan mode. Write a tidy little prompt to tell it you want to change auth from using X to Y, and to do a deep analysis of the entire codebase and prepare a detailed implementation checklist and plan for you both to review. Tell it the plan must include migration of existing user data (assuming your app is already live?). This plan will become the prompt used in the next step - ensure it includes instructions that it must work through the plan systematically and surgically, but not make any other changes not related to switching auth providers.

  3. Then switch to Build mode (but keep High autonomy), and ask it to “work through the implementation checklist and plan incrementally in phases, and pause at natural checkpoints to engage in a 2-way conversation with me: showing me what you have done and confirm what’s next; ask me if you need me to make changes (e.g. DB schema, migrate data to the new system, new Replit secrets, etc), and provide me with relevant data, SQL, etc to make such changes; ask me to test; get my approval before moving to the next phase; address any questions, issues or changes, etc.”

  4. cross your fingers and say a little prayer :blush:

If you decide to brave it and have a go, paste both prompts here for us to review before you hit the Go button.

PS, this guide comes with zero warranty and absolutely no promises that it will work. This is the forefront of technology, you are pioneers, prepare to have it blow up, crash and burn! :blush:

8

Thanks for the follow up.

All sorted now.
I managed to integrate Firebase Auth using Agent 3 without any issues now :slightly_smiling_face:

1 Like