# Let users log in with single sign-on (SSO)

> Let app users sign up and log in with Google, Microsoft Azure, Okta, Auth0, Facebook or Twitter, and control who a provider lets in.

Source: https://tadabase.com/docs/users-security/single-sign-on-sso  
Status: Verified Nov 17, 2026. Checked against the current product

Single sign-on (SSO) lets your app's users sign up and log in with an account they already have at a provider such as Google or Microsoft, instead of a password for your app. You create an app at the provider, paste its keys into **User Settings**, and add the provider's button to your Login and Signup components.

## Providers you can use

| Provider | Fields Tadabase asks for | Guide |
| --- | --- | --- |
| Google | **Client ID**, **Client Secret** | [Let users log in with Google](https://tadabase.com/docs/users-security/single-sign-on-with-google) |
| Azure (Microsoft Entra ID) | **Tenant ID**, **Proxy**, **Client ID**, **Client Secret** | [Let users log in with Microsoft Azure](https://tadabase.com/docs/users-security/sso-with-azure) |
| Okta | **Base URL**, **Client Id**, **Client Secret** | [Let users log in with Okta](https://tadabase.com/docs/users-security/sso-with-okta) |
| Auth0 | **Base URL**, **Client Id**, **Client Secret** | [Auth0](#auth0) below |
| Facebook | **App ID**, **App Secret** | [Facebook](#facebook) below |
| Twitter | **App Key**, **App Secret** | [Twitter](#twitter) below |

> **Note:** Single sign-on is a plan feature. If your plan does not include it, the provider icons in **Login/Signup Methods** show an upgrade badge and Tadabase will not turn the provider on.

## Set up a provider

These steps are the same for every provider. The provider pages and sections below say what to create on the provider's side.

1. **Turn the provider on** In the builder, open **Settings** > **User Settings**, **General** tab. Under **Login/Signup Methods**, click the provider's icon. Its card opens.
2. **Copy the Callback URL** Click **Copy** next to **Callback URL** on the provider's card. Each provider and each app has its own callback URL, which ends in `/sso/callback/<provider>`.
3. **Create an app at the provider** In the provider's developer console, create an OAuth or OpenID Connect app and paste the callback URL as its redirect URI (the provider may call it a redirect URL, callback URL or sign-in redirect URI).
4. **Paste the keys into Tadabase** Copy the ID and secret the provider gives you into the fields on the provider's card, then save.
5. **Add the buttons to your components** Edit your Login component and add **Login With** *provider* **(SSO)**. Edit your Signup component and add **Signup With** *provider* **(SSO)** from **Buttons/HTML**. If **Email** is turned off, use the **Single Sign On (SSO) Form** section of the Login component and the **Single Sign On (SSO)** section of the Signup component.
6. **Test it** Open the live app in a private browser window and sign up, then log in, with the provider.

## Options on every provider card

| Option | What it does |
| --- | --- |
| **Domain Restrictions** | A comma-separated list of email domains, such as `yourcompany.com`. When it is filled in, only accounts whose email ends in one of these domains can sign in with this provider; others see "The email address provided has not been whitelisted." Leave it empty to allow any domain. |
| **Allow auto link to existing account** | When a provider account signs in for the first time and a user with the same email already exists in your app, Tadabase links the two and logs that user in. |
| **Reject unknown identities** (Okta, Auth0, Azure) | **Reject**: a person with no account in your app is refused ("Your organization account is not enrolled in this app."), so you must create users first or let auto link match them by email. **Allow sign-up**: they can register through the Signup component. |
| **Single sign-on only** (shown when Okta, Auth0 or Azure is on) | Turns off password sign-in, password reset, self-serve magic links and sign-up for everyone except the emails under **Break-glass administrators**. Each break-glass sign-in is flagged in the login log. |

## What happens the first time someone uses SSO

- Tadabase needs an email address from the provider. If the provider does not return one, the user sees an error that an email address is required.
- **From a Signup component**: Tadabase creates a new user with the name and email the provider returned, together with anything else the user filled in on the form.
- **From a Login component**: if the provider account is already linked to a user, that user is logged in. If it is not linked and **Allow auto link to existing account** finds no user with the same email, the user sees "Your account is not registered using this method" and must sign up first.
- After the first sign-in the provider account stays linked to the user, so later logins do not depend on the email matching.

## Auth0

1. **Create an application in Auth0** In your Auth0 dashboard, create a Regular Web Application.
2. **Add the callback URL** Paste Tadabase's **Callback URL** from the Auth0 card into the application's allowed callback URLs.
3. **Fill in the Auth0 card** **Base URL**: your Auth0 domain without `https://`, for example `your-tenant.us.auth0.com`. Tadabase adds `https://` itself. **Client Id** and **Client Secret**: from the application's settings.

Tadabase asks Auth0 for the `openid`, `profile` and `email` scopes.

## Facebook

1. **Create an app at Meta for Developers** Create an app with Facebook Login and make sure it can read the user's email address.
2. **Add the callback URL** Paste Tadabase's **Callback URL** from the Facebook card into Facebook Login's valid OAuth redirect URIs.
3. **Fill in the Facebook card** Copy the app's ID into **App ID** and its secret into **App Secret**.

## Twitter

1. **Create an app in the X (Twitter) developer portal** Turn on user authentication for the app and allow it to request the user's email address. Without the email, Tadabase cannot sign the user in.
2. **Add the callback URL** Paste Tadabase's **Callback URL** from the Twitter card into the app's callback URLs.
3. **Fill in the Twitter card** Copy the app's API key into **App Key** and its secret into **App Secret**.

## SSO on copied apps

The callback URL contains your app's ID, so a copy of an app has a different callback URL from the original. To let the copy use the same provider app, open the copy's **User Settings**, copy its **Callback URL**, and add it as an extra redirect URI in the provider app you already have.

## Common problems

| Message the user sees | What to check |
| --- | --- |
| The email address provided has not been whitelisted. | The account's domain is not in the provider's **Domain Restrictions**. |
| Your account is not registered using this method | The user tried the Login component before signing up. Have them use the Signup component, or turn on **Allow auto link to existing account** if they already have a user with the same email. |
| Your organization account is not enrolled in this app. Please contact the app administrator. | **Reject unknown identities** is set to **Reject** and the person has no user in your app. |
| An error occurred; please try again or contact the app admin. | Check that the callback URL at the provider matches the one on the card exactly and that the ID and secret are correct. |
