How to integrate MS2.0 with Firebase to share login credentials between web and mobile?
Hello! Does anyone have experience integrating Memberstack with Firebase backend? I recently migrated a client's Webflow user accounts to Memberstack. They've hired another dev to build out a mobile app for them, he's using Firebase auth and ideally we'd like to be able to have users use the same login credentials from the website (Memberstack) to access the mobile app.
The dev makes it seem like Memberstack 2.0 is too limited to do this.. any help would be greatly appreciated!
Comments
5 comments
It would be helpful if the dev could specify on what’s the limitation they refer. Maybe a different techonology gives them the flexibility they are looking for.
Firebase is a full backend as a service. It provides a lot of functionality that Memberstack has not. But it can get REALLY expensive if you’re not careful to optimize the queries.
There has been some challenges in integrating Memberstack on a mobile environments mentioned in this channel. MS client library is oriented to web, not mobile. While it could be adapted and some mobile dev frameworks could partially support it, there might be some situations where it would not be enough and the dev might have to spend more time and effort figuring a solution so it fits the chosen technology.
Probably you should discuss it with them first to ask them what are the business rules and to see if every scenario fit, and can scale before committing to a specific technology
In his words, Memberstack has disabled the ability to login users outside of a browser experience - is that generally true with V2.0?
My understanding is that we can still log in/auth users to Memberstack on the server-side, right? Forgive me if I'm not understanding correctly.
Uhm... probably would need input from the Memberstack team on this but personally, I don't think that's true. If you're using the REST endpoints found in the MemberstackDOM library, you can login... their backend doesn't have such limitation
I'm not sure if the dev refers to the MemberstackDOM library... then, it's limited to the browser because that library uses Javascript and needs a web environment to run. The limitation that people have reported using Memberstack is not being able to login using a SSO Provider like Google, Facebook and so on because that functionality opens up a browser to login.
Yeah the dom package is browser only, but with the admin APIs you can verify requests - so, I think the best flow would be to have them log in in the browser, then pass the JWT to your app, and then verify it with the admin API.
I'm not sure if you can actually authenticate users with the admin api - Josh Lopez what do you think?
cc Tyler Bell
Please sign in to leave a comment.