I want to use Bubble to build a new section of an existing website which has an authentication and sends requests to the API based on the authenticated user. This has to be transparent for the end user.
Would it make sense? What would be your recommended approach?
To do so, I was thinking the Bubble app should be able to communicate with the same API, thus reusing the tokens, session… (local storage and/or cookies.) I planned to get inspiration from the existing authentication plugins with external providers (Google, Facebook…) Ideally, the authentication should be automated (e.g. redirect to the existing website, then redirect back to Bubble), at worst a button. But having a new user/password is a no-go.
Another (complementary?) way of seeing that integration is that a Bubble user is created on-the-fly and Bubble auto-marks the user as signed in. This would allow Bubble to use its authentication features, thus its own database.
I’m open to writing a custom plugin if required (I’m a Bubble newbie but a developer). The other website is made with custom development and can be extended if required (especially the API).
Thanks a lot!
Edit: I’ve noticed there is a close topic, which does not mention the authentication challenge. I’m not (yet?) worried about the challenged mentioned there.