Comment on page
Single sign-on (SSO)
At its core, single sign-on (SSO) is an authentication service that allows a user to use one set of credentials (like a username and password) to access multiple applications. Think of it as having a master key that can open multiple doors in a building rather than juggling a bulky keyring.
Many companies use SSO to let users sign into a variety of third-party applications and services. For instance, when you log in to a new web service and are offered the option to "Sign in with Google" or "Sign in with Facebook," you're seeing SSO in action.
Increasingly, the tools used by members of enterprise organizations are scattered across a large catalog of online services. For example, a company may use one piece of software for project management, and a different one for handling inventory and finances. Managing multiple login credentials for each tool isn't just inconvenient—it's a security concern. That's where SSO comes into play. With SSO, members of your organization only need one set of credentials to access all their apps.
SSO simplifies the login process and helps your team spend less time on password-related tasks and more time being productive. From a security standpoint, having one robust password means you're not juggling a myriad of potentially weak ones. From a managerial perspective, monitoring a single authentication point makes it easier to spot any IT issues.
This is why we offer a secure SSO solution that lets your members log into their Bubble account using widely adopted, secure identity providers. We’re compatible with any identity provider that's either SAML or OIDC, including (but not limited to) the following:
A major advantage of this system is centralization. If a user changes their password or if their access permissions are updated, these changes are reflected across all applications linked to their credentials. It keeps things consistent and secure. With SSO, you're not just getting a streamlined login experience; you're investing in a secure and efficient operational future.
At its core, SSO is a way to manage user authentication across multiple SaaS applications and services. But what's happening under the hood to make this possible? Let’s first break down the step-by-step logic of SSO in action:
- 1.Initial authentication: The process starts when a member logs into Bubble using SSO. This initial sign-in is verified by an identity provider (IdP) such as Auth0 and Okta, the trusty guardian of user identity. Think of the IdP as a gatekeeper, ensuring users are genuinely who they claim to be.
- 2.Token creation: Once the IdP authenticates a user's credentials, it creates a special “token.” This token doesn't store sensitive data like passwords. Instead, it's like a “ticket” confirming that the user has been verified.
- 3.Use across apps: As users move between different connected applications, this token is their passkey. Instead of knocking on the door of each new application with a separate password, the token shows they've already been vouched for. The apps trust the IdP's verification, allowing users straightforward access.
If you’re interested in setting up SSO for your organization, please get in touch with our Sales team, and we’ll provide you with the instructions to get the process started. After SSO has been enabled and set up, your organization admin can start inviting team members. For your first-time SSO login, use the link bubble.io/login/sso. If you have an existing Bubble account, you will be redirected to login via your existing login method to authenticate yourself. After logging in, you will be directed to migrate and consent to your new permissions in your organization. In every login thereafter, you would use the SSO login with your IdP.
Admins can easily add new members in bulk by entering user emails separated by commas. Each member will receive an email after they have been added, and will be redirected to http://bubble.io/login/sso upon their next login.
- If a member has an existing Bubble account, they will need to first authenticate themselves by logging in using their original method.
- If a member does not have a Bubble account, their account will be created for them automatically, using just-in-time (JIT) provisioning
After their first login, members will be required to use SSO to login to Bubble and will not be able to login via other authentication methods.
Members can be removed by opening the dropdown contextual menu in the list of members and selecting Remove member.
If you remove a member, they will be scheduled for deletion within seven days, with no ability to login via Bubble. However, you can reinstate their membership within this seven-day window if you’ve made a mistake.
Members cannot transfer apps or change the permission settings in the Collaboration tab, unless they are the creator of that app. Members can create as many apps on the Free plan as needed, but only the admin can change the plan or buy plugins.
All signed-out users will see the Log in with SSO option in the bottom corner of Bubble’s login form. Click this to be taken to the SSO form.
The first step in the SSO process is to submit your email address. Bubble will automatically recognize which organization you belong to.
You’ll then be taken to the sign-in form for the IdP that your organization uses.
After signing in, you’ll be sent to the Bubble platform home screen, where you will see all your organization’s applications if you are an admin.