Step 1 | Get started with SSO
Single Sign-On (SSO) lets people sign in to your Base44 app using an external identity provider that supports OpenID Connect (OIDC), such as Google, Microsoft, GitHub, Okta, Apple, or Kakao, instead of creating a separate login for your app. To find your Base44 app ID and redirect URI:- Go to your app editor in Base44.
- Check your browser’s address bar and find the app ID between
/apps/and/editor/in the URL. - Build your redirect URI by replacing
{{APP_ID}}in this format with your app ID:https://app.base44.com/api/apps/{{APP_ID}}/auth/sso/callback
Example: From app URL to redirect URI
Example: From app URL to redirect URI
https://app.base44.com/apps/686404784ac37377589a1f7f/editor/...Here, 686404784ac37377589a1f7f is the app ID. Plug that into the format:https://app.base44.com/api/apps/686404784ac37377589a1f7f/auth/sso/callbackThis is the redirect URI you’ll enter with your SSO provider.- When you choose a provider, Base44 lists every callback URL for your app so you can copy them. Register each one with your identity provider as an allowed redirect URI. Some providers, such as ClassLink, reject a login when the redirect URI does not exactly match a registered value.
- By default, an SSO login runs through
app.base44.comeven when your app has a custom domain. To keep it on your own domain, turn on Use this app’s custom domain as the SSO callback. This is off by default, and you need a verified custom domain on the Domains tab before you can turn it on. When you do turn it on, register the custom-domain callback URL with your provider as well. - Most providers, including Google, Microsoft, and Okta, work with the default. Turn the custom domain callback on for providers that require the redirect URI to match your domain, such as ClassLink, Clever, and strict Azure or Entra policies.
- If your app uses your workspace SSO provider instead of its own, Base44 shows a workspace app login callback URL. Ask your workspace admin to add that URL to the workspace identity provider. Learn more about enforcing SSO across all workspace apps.
Step 2 | Choose your provider
Start by choosing the identity provider your team already uses. You can pick a built-in option (Google, Microsoft, GitHub, or Okta), or use Advanced / Manual configuration to connect any OIDC provider, including Kakao, or your own IdP.Google Workspace
Microsoft 365 / Entra ID
GitHub
Okta
Advanced / Manual configuration
Google Workspace
Use Google Workspace as your SSO provider with an OAuth 2.0 Web application. First, create an OAuth 2.0 client in the Google Cloud console for your project, then add those credentials in Base44.- A client ID and client secret from Google Cloud
- Your app’s redirect URI from Step 1
- Click Dashboard in your app editor.
- Click Settings.
- Click Authentication.
- Click Set Up next to Single sign-on (SSO).
- In Select SSO Provider, choose Google Workspace.
- Enter your Client ID and Client Secret from Google.
- Keep Scope as
openid email profile. - Leave Discovery URL set to the default value.
- Click Enable SSO.

Google Workspace SSO settings in your Base44 app
Microsoft
Use Microsoft Entra ID (Azure AD) as your SSO provider through your Azure portal. To set up SSO for a whole enterprise workspace rather than a single app, see SSO for Microsoft Entra ID. Base44 supports both single-tenant and multi-tenant Microsoft configurations. What you enter in the Tenant ID field controls which accounts can log in.- Application (client) ID and client secret from Azure
- The redirect URI from Step 1, added to your Azure app registration
User.Readand standard OpenID Connect permissions (openid,email,profile) granted in your Azure app registration
- Click Dashboard in your app editor.
- Click Settings.
- Click Authentication.
- Click Set Up next to Single sign-on (SSO).
- In Select SSO Provider, choose Microsoft Azure AD.
- Enter your Azure Client ID (Application (client) ID) and Client Secret.
- In the Tenant ID field, enter a value based on which accounts you want to allow:
- Your directory (tenant) ID from Azure: Only people from your specific organization.
common: Personal Microsoft accounts and work/school (Microsoft 365) accounts.organizations: Work and school accounts only (Microsoft 365).
- Keep Scope as
openid email profile. - The Discovery URL fills in automatically based on the tenant ID you entered. Confirm it looks correct before continuing.
- Click Enable SSO.

Microsoft Azure AD SSO settings in your Base44 app
GitHub
Use a GitHub OAuth app as your SSO provider. Create an OAuth app in GitHub Developer Settings, then connect it in Base44.- A GitHub OAuth app created in GitHub Developer Settings
- The app’s authorization callback URL set to your redirect URI from Step 1
- Client ID and client secret generated by GitHub for your OAuth app
- Click Dashboard in your app editor.
- Click Settings.
- Click Authentication.
- Click Set Up next to Single sign-on (SSO).
- In Select SSO Provider, choose GitHub.
- Enter your GitHub Client ID and Client Secret.
- Keep Scope as
user:email. - Keep the default Auth Endpoint, Token Endpoint, and Userinfo Endpoint values for GitHub.
- Click Enable SSO.

GitHub SSO settings in your Base44 app
Okta
Use Okta as your SSO provider. In your Okta Admin Console, create an OIDC Web application for your Base44 app, then add the credentials in Base44.- Okta client ID and client secret
- Your Okta subdomain (the part before
.okta.com, for exampleyour-company)
- Click Dashboard in your app editor.
- Click Settings.
- Click Authentication.
- Click Set Up next to Single sign-on (SSO).
- In Select SSO Provider, choose Okta.
- Enter the following:
- Client ID: Your Okta client ID.
- Client Secret: Your Okta client secret.
- Okta Domain: Enter this in whichever form matches your Okta org:
- Your Okta subdomain, for example
your-company. - Your full custom Okta URL domain, for example
login.your-company.com. - The issuer URL including the authorization server path, for example
https://login.your-company.com/oauth2/default, if your Okta org uses API Access Management with custom authorization servers.
- Your Okta subdomain, for example
- Scope: Keep
openid email profile. - Discovery URL: This is generated from your Okta domain and marked Auto. You can edit it if you need to point Base44 somewhere else, and it then shows as Modified. To go back to the generated value, click Reset to auto.
- Click Enable SSO.

Okta SSO settings in your Base44 app
Advanced / Manual configuration
Use Advanced / Manual Configuration to connect any OIDC compatible identity provider that is not covered by the built in options. This includes providers such as Kakao, as long as they support OIDC and you configure them with the correct details from your provider.- OIDC client credentials from your provider
- The redirect URI from Step 1, registered with your provider
- Discovery URL or all OIDC endpoints from your provider
- Required scopes (
openid email profileor equivalent)
- Click Dashboard in your app editor.
- Click Settings.
- Click Authentication.
- Click Set Up next to Single sign-on (SSO).
- In Select SSO Provider, choose Advanced / Manual Configuration.
- Fill in the following fields using your provider’s values:
- Name: A name for this SSO configuration (for example,
Auth0,Keycloak,Kakao, or your identity provider name). - Client ID: Your OIDC client ID.
- Client Secret: Your OIDC client secret.
- Scope: Enter
openid email profile. - Discovery URL: Your provider’s discovery URL, if available.
- Auth Endpoint, Token Endpoint, Userinfo Endpoint, Jwks Uri: If you are not using a discovery URL, paste each endpoint from your provider’s documentation.
- Name: A name for this SSO configuration (for example,
- (Optional) Turn off either of these settings if your provider rejects it. Both are on by default:
- Use PKCE (recommended): Adds the standard OAuth 2.1 PKCE challenge to login. Turn it off only for providers that reject unknown OAuth parameters, such as ClassLink or older Shibboleth and ADFS deployments.
- Request offline access: Asks your provider for a refresh token. Turn it off only for providers that reject it, such as the ones above. It has no effect for providers that use
response_mode=form_post, such as Apple.
- Click Enable SSO.

Advanced / Manual SSO configuration in your Base44 app
Step 3 | Test your SSO login
After you set up SSO, sign in to your app with it to check that everything works. To test your SSO login:- Log out of your app if you are currently signed in.
- Go to your app’s login screen.
- Click Log in with SSO or select the provider you configured.
- Sign in using an email address from your approved domain.
Automatically giving access to your app
Give people access to your app as soon as they sign in through SSO, with no invite. Auto-admit is a per-app setting that overrides your workspace default. It is off by default.- Click Dashboard in your app editor.
- Click Settings.
- Click Authentication.
- Next to your SSO provider, click Configure.
- Turn Auto-admit SSO users on or off.
- Click Save SSO Settings, or Enable SSO if the app uses your workspace SSO provider.
- Turning off auto-admit stops new people being admitted. It doesn’t remove anyone who already has access. To stop someone signing in again, remove or suspend them in your identity provider.
- If your workspace enforces SSO for all apps, Auto-admit SSO users takes effect immediately. If the setting is disabled, check that the app is private and that SSO is the only enabled sign-in method.
Offering other sign-in methods
An app that uses SSO can also let people sign in with Google, Microsoft, Facebook, Apple, or email and password. Use it when one app serves people inside and outside your company. For example, your staff sign in through your company’s identity provider, while customers, patients, or contractors without a company account sign in with Google. You choose the email domains that must still use SSO, such as your company’s domain. Anyone whose email is on one of those domains can only sign in with SSO. Everyone else can use any sign-in method your app offers. You can do this after you set up and turn on SSO for your app. It’s off by default. To offer other sign-in methods alongside SSO:- Go to your app editor.
- Click Dashboard.
- Click Settings.
- Click Authentication.
-
Under Single sign-on (SSO), type a domain in Email domains that must use SSO, then press Enter. Repeat for each domain, including subdomains such as
mail.example.com, which don’t matchexample.com. -
Turn on Allow other sign-in methods alongside SSO.

Allowing other sign-in methods alongside SSO
- Turn on each sign-in method you want to offer alongside SSO, such as Google or email and password.
- (Optional) If your app uses custom login pages, click Send to chat under Single sign-on (SSO). The AI adds the SSO button and a button for each sign-in method you turned on to your login and register pages.
- To stop offering other sign-in methods, turn off Allow other sign-in methods alongside SSO. Google, Microsoft, Facebook, and Apple sign-in stop working, so people who signed up with one of them can’t sign in that way anymore. Email and password sign-in keeps working while it’s on, so turn it off too if you want SSO to be the only way in. If you remove every domain from the list, Base44 turns the setting off for you.
- If someone whose email is on one of your domains tries another sign-in method, they see a message asking them to sign in with SSO.
- People who are already signed in stay signed in when you change this setting.
Scopes and user details
When someone signs in with SSO, Base44 reads a few details from your identity provider and uses them to create their user record in your app. Knowing what Base44 reads helps you choose your scopes and plan how your app handles roles.Choosing scopes
Base44 sends the Scope field to your provider exactly as you enter it. Base44 needs each person’s email address, so always include the scopes that return it,openid email profile for OIDC providers or user:email for GitHub.
You can add any other scopes your provider allows, such as a scope for one of its APIs. Extra scopes don’t change what Base44 saves about the person. They’re useful when your app’s backend functions call your provider with the person’s access token, which you get with the SSO module of the SDK.
Details Base44 saves
Base44 saves only 2 details from your provider in the person’s user record: their email and their name. It doesn’t save anything else, such as profile pictures, groups, roles, or custom claims, and you can’t set up your own mappings. A person’s role in your app always comes from Base44, such as the role you give them when you invite them.- Email: Required. Base44 reads the
emailclaim from the ID token, or from your provider’s userinfo endpoint if the ID token doesn’t include it. For Microsoft Entra, Base44 uses the person’s user principal name when there’s noemailclaim and it’s an email address. If Base44 can’t find an email, sign-in fails withEmail not returned by OAuth provider. - Name: Base44 reads the
nameclaim, or the GitHub name or username, and saves it as the person’s full name. If there’s no name, Base44 uses the part of the email before the @. The name is saved only the first time the person signs in, so later changes in your provider don’t update it.
FAQs
Click a question to learn more about SSO.Do I need to set up SSO if I only use one login?
Do I need to set up SSO if I only use one login?
What is a redirect URI and where do I use it?
What is a redirect URI and where do I use it?
https://app.base44.com/api/apps/{{APP_ID}}/auth/sso/callbackWhat is a discovery URL and do I need to add it?
What is a discovery URL and do I need to add it?
- For Google, you do not need to enter a discovery URL. Base44 handles it automatically.
- For Microsoft (Azure / Entra ID), the discovery URL fills in automatically based on the tenant ID you enter. The format is
https://login.microsoftonline.com/{TENANT_ID}/v2.0/.well-known/openid-configuration, where{TENANT_ID}is your directory tenant ID,common, ororganizations. - For Okta, the discovery URL fills in automatically from your subdomain, but many setups need a different URL (usually the
/oauth2/defaultform) so Okta returns your email. See the Okta setup notes for the exact format. - For GitHub, you can leave the discovery URL field blank.
- For Advanced / Manual providers such as Kakao, follow your provider’s documentation. If they give you a discovery URL, paste it into the Discovery URL field. If not, enter the individual endpoints instead.
What if I see an error when logging in using SSO?
What if I see an error when logging in using SSO?
- Your redirect URI in Base44 exactly matches the one in your provider’s dashboard.
- Your client ID, client secret, and discovery URL, if you use one, are correct.
- The scope is
openid email profile, or an equivalent email scope, in both your provider’s configuration and Base44.
Why does the Google login still show "base44.com" instead of my app name after setting up custom SSO?
Why does the Google login still show "base44.com" instead of my app name after setting up custom SSO?
base44.com as the app name or badge, your custom Google project has not been fully approved yet. Once Google approves your project, your app’s own name or branding appears instead of base44.com.How can I make sure my app name appears in the Google login instead of "base44.com"?
How can I make sure my app name appears in the Google login instead of "base44.com"?
base44.com.Which applications commonly use SSO or OAuth?
Which applications commonly use SSO or OAuth?