You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm considering the possibility of using Firebase Auth instead of the native wasp authentication and I'm looking for advice.
What would be the best strategy in my case? Does it even make sense?
If it's feasible, should I add a new auth provider for wasp? Or just replace wasp auth in the open-saas template?
How would you do this if you needed the same?
I'd appreciate any input. Thank you.
The text was updated successfully, but these errors were encountered:
I would suggest using the Wasp Auth, as it's a built-in full-stack solution with managed, but customizable, UI components.
It just works. If you haven't given it a try yet, I suggest you do before ultimately making your decision.
If you still prefer to use Firebase Auth then you won't configure auth in the main.wasp file and will be responsible for creating all your own auth components and dealing with authenticated users on your servers.
Thank you!
The thing is I already have users in Firebase and I have no plans to migrate them. So I wanted to build a companion web app that they could use as well.
Would migrating the users be hard? I assume you could write a script for that. If you decide to go that route, let us know. I'm sure @infomiho (the dev responsible for Wasp Auth) could offer some tips here.
Hi!
I'm considering the possibility of using Firebase Auth instead of the native wasp authentication and I'm looking for advice.
What would be the best strategy in my case? Does it even make sense?
If it's feasible, should I add a new auth provider for wasp? Or just replace wasp auth in the open-saas template?
How would you do this if you needed the same?
I'd appreciate any input. Thank you.
The text was updated successfully, but these errors were encountered: