TABLE OF CONTENTS
- Step 1 – Create a SAML 2.0 application in Auth0
- Step 2 – Add users in Auth0 and Atlas
- Step 3 – Configure Single Sign On in Atlas
- Step 4 – Test the connection
- Troubleshooting tips
Step 1 – Create a SAML 2.0 application in Auth0
Sign in to the Auth0 dashboard
Open the Auth0 dashboard in your browser (for example, your tenant URL or the central Auth0 dashboard).
Sign in with an account that has permissions to manage applications and configure SSO.
Create or open the application for Atlas
In the left-hand navigation, go to Applications → Applications.
Create a new application for Atlas, or open the existing one if it already exists.
When creating the application:
Choose a clear name such as “Atlas SAML SSO”.
Select Regular Web Application (or the application type your Auth0 administrator recommends for SAML-based SSO).
Save the application.
Enable and open the SAML2 Web App Addon
Open the Atlas application you just created in Auth0.
Go to the Addons tab.
Enable the SAML2 Web App addon.
Open the SAML2 Web App configuration dialog.
Configure basic SAML settings with Atlas values
In the SAML2 Web App configuration:
On the Settings tab, locate the SAML configuration fields.
Set the audience or entityId value to the Atlas Audience / Entity ID from the Atlas SSO wizard.
Set the callback URL (Assertion Consumer Service URL) to the Atlas Single Sign On URL from the wizard.
If there is a field for Recipient or Destination, use the same Atlas Single Sign On URL, unless your Atlas administrator instructs otherwise.
Save the SAML2 Web App configuration.
Important: Do not use generic values from other documentation. Always use the exact values generated for your Atlas environment.
Configure Auth0 SAML attributes / claims (if required)
Depending on your internal standards, you may control how user attributes are sent in the SAML assertion.
In the SAML2 Web App Settings, review the mappings or user profile section.
Ensure the SAML assertion includes attributes for:
Email address
First name
Last name
Use clear, consistent attribute names that you will later map in Atlas (for example: email, given_name, family_name).
Save the SAML2 Web App configuration.
Download certificate, metadata, and URLs
In the SAML2 Web App configuration (or the Addons summary), locate Identity Provider Metadata, SAML Metadata, or a similar download link.
Download the metadata XML and/or copy the relevant identity provider URLs (for example, Auth0 SAML sign‑in URL and logout URL) and the certificate.
Keep these details handy—you will paste them into Atlas in the next step.
Step 2 – Add users in Auth0 and Atlas
- Add and allow users in Auth0
- In the Auth0 dashboard, go to User Management → Users to create or confirm the accounts that will sign in to Atlas.
- Make sure these users are allowed to authenticate through the Atlas application (for example, via application access rules, enabled connections, or authorization policies in your Auth0 tenant).
- Add the same users in Atlas
- In Atlas, open the user management area.
- Create or confirm user accounts that match the identifiers used in Auth0 (email address, or username for non‑email users).
- Ensure these identifiers match exactly between Auth0 and Atlas so that SSO can map users correctly.
Step 3 – Configure Single Sign On in Atlas
- Configuration name and protocol
Enter a clear configuration name, for example:
“Auth0 Single Sign On”.
Select SAML 2.0 (or the equivalent option) as the protocol, matching what you configured in Auth0.
- Atlas Single Sign On endpoints
In the wizard step labelled Atlas Single Sign On endpoints, review the values shown (Single Sign On URL and Audience / Entity ID).
Confirm these match the values you entered in the Auth0 SAML configuration (for example, the callback URL and audience / entityId).
- Identity provider configuration (Auth0 metadata, certificate, URLs)
In the relevant step of the Atlas wizard, paste the Auth0 identity provider details you collected earlier:
Identity provider metadata (SAML metadata URL or XML)
Certificate
Sign-in URL (and logout URL, if applicable)
Save this configuration step after entering all required values.
- User attribute mapping
Atlas uses several steps in the wizard for attribute mapping. Follow the prompts and map the Auth0 SAML attributes to Atlas user fields:
Map the attribute containing the email address to the Atlas email field.
Map the attribute containing the first name to the Atlas first name field.
Map the attribute containing the last name to the Atlas last name field.
Mapping a phone number attribute is optional and can be skipped.
Confirm that all required mappings are completed. After finishing the wizard, make sure the configuration saves without errors.
Step 4 – Test the connection
Run the test from Atlas
- On the Atlas Single Sign On configuration page for Auth0, select Test connection.
- Atlas will start the test and redirect you to the Auth0-hosted login page .
Expected behaviour
You are redirected to the Auth0 login page sign-in page.
You can successfully sign in with a user who has been assigned to the Atlas application in Auth0.
After successful authentication, you are redirected back to Atlas.
Atlas shows a confirmation that the connection test was successful.
Troubleshooting tips
If the test connection fails:
Confirm that the audience / entityId and callback / Assertion Consumer Service URL in Auth0 exactly match the values shown in the Atlas Single Sign On endpoints step.
- Check that the user is allowed to authenticate to the Atlas application in Auth0 and that the same user exists in Atlas with matching identifiers.
- Verify that the SAML attribute names / claims for email, first name, and last name in Auth0 match the mappings you configured in Atlas.
- Review any error messages in Atlas and in the Auth0 logs (for example, Monitoring → Logs) to identify which part of the configuration needs adjustment.
If you still cannot resolve the issue, submit a ticket with:
A summary of the steps you followed, and
Any error messages or logs you received.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article