Before you begin
Make sure you have:- Owner or admin access to your Base44 enterprise workspace.
- Admin access to your Okta organization.
- Your workspace ID, the string of characters after
/workspace/in your enterprise workspace URL. - Your Okta domain, the part before
.okta.com(for example,your-company).
Set up single sign-on
Create an OIDC application in Okta, allow Base44 to use it, then add its details to your workspace.Step 1: Create an OIDC app
Create the OIDC application that represents Base44 sign-in. To create the app:- In the Okta Admin Console, go to Applications > Applications, then click Create App Integration.
- Set Sign-in method to OIDC - OpenID Connect.
- Set Application type to Web Application.
- Click Next.

Step 2: Configure the app
Set the app name, redirect URIs, and who can use it. To configure the app:- Enter an App name, for example
Base44 - your workspace name. - Under Sign-in redirect URIs, add your workspace callback URL, replacing
{{WORKSPACE_ID}}with your workspace ID:https://app.base44.com/api/workspaces/{{WORKSPACE_ID}}/auth/sso/callback - Under Sign-out redirect URIs, add
https://app.base44.com. - Under Controlled access, choose who can use the app, for example Allow everyone in your organization to access.
- Click Save.

Step 3: Get your credentials
From the app’s General tab, copy:- Client ID
- Client Secret
- Your Okta domain, the subdomain only (for example,
your-company, notyour-company.okta.com).
Step 4: Allow Base44 in your authorization server
Okta only issues tokens to apps that an authorization server policy allows. To add an access policy rule:- Go to Security > API > Authorization Servers, then open the default server.
- On the Access Policies tab, click Add Rule, or edit an existing rule.
- Name the rule (for example,
Allow Base44), set the grant type to Authorization Code, and apply it to your Base44 app (or all clients), all users, and any scopes. - Click Create Rule.
In your Base44 app’s General tab in Okta, turn Federation Broker Mode off. With it on, sign-in can fail with “You are not allowed to access this app.”
Step 5: Add your details in Base44
Add the OIDC app credentials to your workspace. To configure SSO in Base44:- Click your workspace name at the top left of your account.
- Click Settings.
- Click Auth and security.
- Enable the toggle next to Single Sign-On Configuration.
- In Select SSO Provider, choose Okta.
- Enter your Client ID, Client Secret, and Okta Domain (the subdomain only).
- Keep Scope as
openid email profile. - The Discovery URL fills in automatically from your Okta domain.
- Click Enable SSO.

Step 6: Assign users
People can sign in once they are assigned to your Okta app. To assign users:- In your Okta app, go to the Assignments tab.
- Click Assign, then Assign to People or Assign to Groups.
- Select the users or groups that should be able to sign in, then click Assign and Save and Go Back.
FAQs
Select a question below to learn more about Okta SSO.Sign-in fails with 'You are not allowed to access this app'
Sign-in fails with 'You are not allowed to access this app'
Add an access policy rule on the default authorization server (Step 4), turn off Federation Broker Mode in the app’s General tab, and confirm the user is assigned to the app.
Sign-in fails with an email error
Sign-in fails with an email error
Okta’s default authorization server does not always return the
email claim. Set Okta up through Advanced / Manual configuration and use the /oauth2/default Discovery URL so the email is returned. See the note in Step 5.Do I need separate Okta apps for SSO and SCIM?
Do I need separate Okta apps for SSO and SCIM?
Yes. Okta OIDC apps do not support SCIM, so SSO uses an OIDC app and SCIM uses a separate SCIM 2.0 app. See SCIM provisioning for Okta.

