Before you start
You'll need:
An active Okta administrator account.
Access to Atlas with permission to configure single sign-on (SSO).
The Atlas SSO configuration page open in a separate browser tab; you'll be copying values between the two.
Step 1: Set up a SAML app in Okta
Sign into Okta
Go to your Okta sign-in page and sign in with your administrator account.
Complete multifactor authentication if prompted.
Create a new app integration
In the left menu, select Applications.
Click Create App Integration.
When asked to choose a sign-in method, select SAML 2.0.
Continue to the SAML settings page.
Configure SAML settings
Enter the values from your Atlas SSO configuration screen:
In the Single Sign On URL field, paste the Atlas SSO URL shown in the Atlas wizard.
In the Audience URI (Service Provider Entity ID) field, paste the Atlas Audience or Entity ID from the Atlas wizard.
Save your changes.
Step 2: Add users in Okta and Atlas
Add or import users in Okta
In Okta, go to Directory → People.
Add users manually or import them from a CSV file.
Make sure each user has the correct e-mail address, first name, and last name.
Assign users to the Atlas app
Go to Applications and open the SAML app you just created.
Assign the relevant users or groups so they can sign in using SSO.
Add the same users in Atlas
In Atlas, open the user management area.
Create or confirm accounts for the same users, making sure their e-mail addresses match exactly what's in Okta.
Note: User identifiers must match between Okta and Atlas for SSO to work correctly.
Step 3: Configure single sign-on in Atlas
Open the SSO configuration page in Atlas and follow the wizard.
Name and protocol
Enter a Configuration name: for example, Okta SSO.
Select SAML 2.0 as the protocol.
Atlas Single Sign-On endpoints
In step 2 of the Atlas wizard, you'll see the Atlas SSO URL and Audience or Entity ID.
These are the values you pasted into Okta in step 1: confirm they match.
Okta identity provider details
From Okta, download or copy the identity provider metadata (or certificate and SAML endpoints) for your Atlas app.
In step 3 of the Atlas wizard, paste or upload the Okta metadata and certificate as requested.
Save and continue.
Map user attributes
In step 4, map the Okta attributes to Atlas user fields:
E-mail address: Atlas e-mail field.
First name: Atlas first name field.
Last name: Atlas last name field.
Phone number: optional, can be skipped.
Use the exact attribute names from your Okta SAML app.
Additional settings
You can optionally configure:
Force single sign-on: Requires users to sign in through Okta only.
Just-in-time provisioning: Automatically creates Atlas accounts for users signing in for the first time.
Review the settings and save. The configuration should save without errors.
Step 4: Test the connection
In Atlas, select Test connection on the SSO configuration page.
Atlas will redirect you to the Okta sign-in page.
You've set things up correctly if:
You're redirected to the Okta sign-in page.
You can sign in with a user assigned to the Atlas app in Okta.
After signing in, you're redirected back to Atlas.
Atlas shows a confirmation that the connection was successful.
Troubleshooting
If the connection test fails, check the following:
The SSO URL and Audience or Entity ID in Okta exactly match the values shown in Atlas.
The Okta user is assigned to the Atlas SAML app and exists in Atlas with the same identifier.
The SAML attribute names for e-mail, first name, and last name in Okta match the mappings in Atlas.
Review any error messages in Atlas or Okta for further detail.
If you're still stuck, contact your internal administrator or reach out to Atlas support. Include a description of what you've tried and any error messages you've seen.