I am a huge fan of Auth0 and I was really disappointed when I realized no Auth0 integration was available in Bubble, which means no simple solution to propose users to authenticate using multiple existing services (without creating a new account/password couple).
In my opinion, Auth0 is particularly useful when you provide B2B software and need to connect using your customer’s identity provider. It is also nice to use in a B2C world.
So here it is as a plugin that you can now install to benefit from all the social integration that Auth0 provide (Google, Facebook, Linkedin, Github, Microsoft, Dropbox, Twitter, Amazon, Paypal, AD/LDAP, ADFS, Google Apps, Office 365, SAMLP, etc… )
So far, the tested integrations are : Google, Linkedin and Twitter. I’m pretty confident that a lot of the other integrations will work out of the box but if it is not the case, please contact me !
Don’t hesitate to contact me if you have questions or remarks about this plugin.
Finally, an Auth0 plugin for Bubble!! Super quick to set up, and works like a charm (I tested with Google and Email+Password so far), thank you @vparpoil!
Thanks for your feedback @Lucien !
I have got some other feedback (@petit-ricard) that allowed me to craft tow new functionalities that have been released today :
Ability to select which provider to use when being redirected to Auth0. This allow to display one button for Google and one other for Twitter, as demonstrated here : https://plugin-auth0-demo.bubbleapps.io
New action to retrieve the user access token that is provided by the social identity provider (ie: Google, Facebook, etc). This action requires additional setup in auth0 described in the lower part of the demo website.
What advantage is there to creating an email based bubble user (real, or fake) yourself like that. Instead of using auth0 as a bubble social signon ? i.e. so the bubble user is the auth0 sub.
Hi @NigelG,
Thanks for your interest. Actually Auth0 is not listed as a login service of the “Signup/login with a social service” so I don’t see how do you use :
auth0 as a bubble social signon
Can you give me some more detail ?
What I read from the docs is similar to what is being set up here :
When a user signs up with a social network (Facebook) in Bubble, a new user is created in the database, similarly to a traditional sign up flow with email and password. The main difference is that the way to login for the user, once logged out, will not be by entering his password (since he didn’t define one), but by logging in with Facebook
If you use the AUTH0 OAUTH signup in Bubble as a “sign up with a social network” Bubble should just create a user for you (the id is in fact the auth0 sub).
I wondered why the plugin suggests using “create a user for someone else” and using a temp password instead of the standard social signup ?
Does Auth0 give the app access to the access tokens for use in workflow without the user being logged in? I like the idea of a simplified authentication process, but my app does a lot of checking/receiving of data while the user isn’t logged in and I need to be able to run API workflows with the access tokens.
I did some testing using the plugin this morning and was able to get a LinkedIn token which I used in an api call to get the profile, so that’s a start. Next up is to explore where the token refresh is handled.
Hi Keith,
The plugin does not provide yet refresh tokens for Auth0, so it’s impossible for now to get access to the provider API (like google API) when offline.
It’s a great idea though !
I will look into it but it’s likely to take some time because of choices I made to give a faster UX to the login process (I used a simpler auth flow rather than the classical login flow). I will at the same time look into @NigelG great suggestion to see how it may fit in the plugin and help regarding this matter. Thanks a lot Nigel for the printscreens !! I had no idea that the Authentification dropdown was helpful here
If someone from the Bubble team is reading here: documentation for plugin builders could benefit of some improvements…
I followed the plugin setup steps, but perhaps I’m missing an important part. The plugin or perhaps Bubble itself is throwing the following errors in the console.
Error - Element index - Please include an email
x5:formatted:18056 Workflow failed: Please include an email
x5:formatted:4349 Error - Action Auth0 - server verification - Please include an email
x5:formatted:4349 Error - Element index - Please include an email
Tips : Instead of User ID key path you can use email instead of sub
If an user auth0 with google or email (same email) it will return existing user instead of creating a new one
I’m running into an issue with this plugin because I cannot pass a logout URL to Auth0.
This is way Auth0 always redirects back to the same page when Logging in and after Logout.
Did anyone manage to detect in Bubble when the users actually logged out?
Hi Louis,
There is at the moment no parameter for a logout redirect Url and it seems to be missing. I will add this functionality to the plugin by the end of the week.
Can you confirm that you are using the SingleLogout action ?
its now working with the following settings