Configure Federated Authentication from Okta¶
This guide shows you how to configure federated authentication using Okta as your IdP .
After integrating Okta and Atlas, you can use your company's credentials to log in to Atlas and other MongoDB cloud services.
If you are using Okta's built-in MongoDB Cloud app, you can use Okta's documentation.
If you are creating your own SAML app, use the procedures described here.
Prerequisites¶
To use Okta as an IdP for Atlas, you must have:
- An Okta account.
- A custom, routable domain name.
Procedures¶
Throughout the following procedure, it is helpful to have one browser tab open to your Atlas Federation Management Console and one tab open to your Okta account.
Configure Okta as an Identity Provider¶
Add a new application to your Okta account¶
- In the Okta top navigation, click the Applications tab.
- Click the Add Application button.
- Click the Create New App button.
- Select Web for the Platform field.
- Select SAML 2.0 for the Sign on method field.
- Click the Create button.
Create Okta SAML integration¶
- Fill in the App name text field with your desired application name.
- Optionally, add a logo image and set app visibility.
- Click the Next button.
Download Okta certificate¶
- Click the Download Okta Certificate button.
- Rename the downloaded file to have a
.cer
extension instead of.cert
.
Navigate to the Federation Management Console¶
- Log in to Atlas.
- Use the dropdown at the top-left of Atlas to select the organization for which you want to manage federation settings.
- Click Settings in the left navigation pane.
- In Manage Federation Settings, click Visit Federation Management App.
Create a new Identity Provider¶
- In the FMC dashboard, click the Manage Identity Providers button.
- Click the Setup Identity Provider button.
Enter SAML settings¶
In the FMC dashboard, fill in the data fields with the following values:
Field Value Configuration Name A descriptive name of your choosing. Issuer URI and Single Sign-On URL Click the Fill With Placeholder Values button to the right of the text fields. You will get the real values from Okta in a later step. Identity Provider Signature Certificate Click the Choose File button to upload the .cer
file you received from Okta earlier.Request Binding HTTP POST Response Signature Algorithm SHA-256 Apply to Organizations Select organizations to connect to this IdP. When users authenticate through Okta for the first time, Atlas grants them membership in the selected organizations. Manage organization mapping to choose what role these users have within the selected organizations. - Click the Next button.
Create SAML Integration¶
In this step, copy values from the Atlas FMC to the Okta Create SAML Integration page.
Okta Data Field Value Single sign on URL Use the Assertion Consumer Service URL from the Atlas FMC.
Checkboxes:
- Check Use this for Recipient URL and Destination URL.
- Clear Allow this app to request other SSO URLs.
Audience URI (SP Entity ID) Use the Audience URI from the Atlas FMC. Default RelayState Leave blank. Name ID format Unspecified Application username Email Update application username on Create and update Click the Click Show Advanced Settings link in the Okta configuration page and ensure that the following values are set:
Okta Data Field Value Response Signed Assertion Signature Signed Signature Algorithm RSA-SHA256 Digest Algorithm SHA256 Assertion Encryption Unencrypted - Leave the remaining Advanced Settings fields in their default state.
Scroll down to the Attribute Statements (Optional) section and create four attributes with the following values:
Name Name Format Value email Unspecified user.email firstName Unspecified user.firstName lastName Unspecified user.lastName memberOf Unspecified user.groups ImportantThe values in the Name column are case-sensitive. Enter them exactly as shown.
NoteThese values may be different if Okta is connected to an Active Directory. For the appropriate values, use the Active Directory fields that contain a user's first name, last name, and full email address.
- Click the Next button in the Okta configuration.
- Select the radio button marked I'm an Okta customer adding an internal app.
- Click the Finish button.
Copy information back to the Atlas FMC¶
On the Okta application page, click View Setup Instructions in the middle of the page.
NoteThe Okta setup instructions appear in a new browser tab.
- In the Atlas FMC , click the Finish button to return to the Identity Providers page. Click the Modify button for your newly created IdP .
Fill in the following text fields:
FMC Data Field Value Issuer URI Use the Identity Provider Issuer value from the Okta Setup Instructions page. Single Sign-on URL Use the Identity Provider Single Sign-On URL value from the Okta Setup Instructions page. - Close the Okta setup instructions browser tab.
- Click the Next button on the Atlas FMC page.
- Click the Finish button the FMC Edit Identity Provider page.
Assign users to your Okta application¶
- On the Okta application page, click the Assignments tab.
- Ensure that all your Atlas organization users who will use the Okta service are enrolled.
Map your Domain¶
Mapping your domain to the IdP lets Atlas know that users from your domain should be directed to the Login URL for your identity provider configuration.
When users visit the Atlas login page, they enter their email address. If the email domain is associated with an IdP, they are sent to the Login URL for that IdP.
You can map a single domain to multiple identity providers. If you do, users who log in using the MongoDB Cloud console are automatically redirected to the first matching IdP mapped to the domain.
To log in using an alternative identity provider, users must either:
- Initiate the MongoDB Cloud login through the desired IdP , or
- Log in using the Login URL associated with the desired IdP .
Use the Federation Management Console to map your domain to the IdP :
Open the Federation Management Console.¶
- Log in to Atlas.
- Use the dropdown at the top-left of Atlas to select the organization for which you want to manage federation settings.
- Click Settings in the left navigation pane.
- In Manage Federation Settings, click Visit Federation Management App.
Enter domain mapping information.¶
- Click Add a Domain.
- On the Domains screen, click Add Domain.
Enter the following information for your domain mapping:
Field Description Display Name Name to easily identify the domain. Domain Name Domain name to map. - Click Next.
Choose how to verify your domain.¶
You can choose the verification method once. It cannot be modified. To select a different verification method, delete and recreate the domain mapping.
Select the appropriate tab based on whether you are verifying your domain by uploading an HTML file or creating a DNS TXT record:
Upload an HTML file containing a verification key to verify that you own your domain.
- Click HTML File Upload.
- Click Next.
- Download the
mongodb-site-verification.html
file that Atlas provides. - Upload the HTML file to a web site on your domain. You
must be able to access the file at
<https://host.domain>/mongodb-site-verification.html
. - Click Finish.
Verify your domain.¶
The Domains screen displays both unverified and verified domains you've mapped to your IdP . To verify your domain, click the target domain's Verify button. Atlas shows whether the verification succeeded in a banner at the top of the screen.
Associate Your Domain with Your Identity Provider¶
After successfully verifying your domain, use the Federation Management Console to associate the domain with Okta:
Click Identity Providers in the left navigation.¶
For the IdP you want to associate with your domain, click next to Associated Domains.¶
Select the domain you want to associate with the IdP .¶
Click Confirm.¶
Test Your Domain Mapping¶
Before you begin testing, copy and save the Bypass SAML Mode URL for your IdP . Use this URL to bypass federated authentication in the event that you are locked out of your Atlas organization.
While testing, keep your session logged in to the Federation Management Console to further ensure against lockouts.
To learn more about Bypass SAML Mode, see Bypass SAML Mode.
Use the Federation Management Console to test the integration between your domain and Okta:
In a private browser window, navigate to the Atlas log in page.¶
Enter a username (usually an email address) with your verified domain.¶
If your verified domain is mongodb.com
, enter
alice@mongodb.com
.
Click Next.¶
If you mapped your domain correctly, you're redirected to your IdP to authenticate. If authenticating with your IdP succeeds, you're redirected back to Atlas.
You can bypass the Atlas log in page by navigating directly to your IdP 's Login URL. The Login URL takes you directly to your IdP to authenticate.
(Optional) Map an Organization¶
Use the Federation Management Console to assign your domain's users access to specific Atlas organizations:
Open the Federation Management Console.¶
- Log in to Atlas.
- Use the dropdown at the top-left of Atlas to select the organization for which you want to manage federation settings.
- Click Settings in the left navigation pane.
- In Manage Federation Settings, click Visit Federation Management App.
Connect an organization to the Federation Application.¶
Click View Organizations.
Atlas displays all organizations where you are an
Organization Owner
.Organizations which are not already connected to the Federation Application have Connect button in the Actions column.
- Click the desired organization's Connect button.
Apply an Identity Provider to the organization.¶
From the Organizations screen in the management console:
- Click the Name of the organization you want to map to an IdP .
On the Identity Provider screen, click Apply Identity Provider.
Atlas directs you to the Identity Providers screen which shows all IdPs you have linked to Atlas.
- For the IdP you want to apply to the organization, click Modify.
- At the bottom of the Edit Identity Provider form, select the organizations to which this IdP applies.
- Click Next.
- Click Finish.
Connect an organization to the Federation Application.¶
- Click Organizations in the left navigation.
- In the list of Organizations, ensure that your desired organization(s) now have the expected Identity Provider.
(Optional) Configure Advanced Federated Authentication Options¶
You can configure the following advanced options for federated authentication for greater control over your federated users and authentication flow:
The following advanced options for federated authentication require you to map an organization.
Sign in to Atlas Using Your Login URL¶
All users you assigned to the Okta application can log in to Atlas using their Okta credentials on the Login URL. Users have access to the organizations you mapped to your IdP .
You can map a single domain to multiple identity providers. If you do, users who log in using the MongoDB Cloud console are automatically redirected to the first matching IdP mapped to the domain.
To log in using an alternative identity provider, users must either:
- Initiate the MongoDB Cloud login through the desired IdP , or
- Log in using the Login URL associated with the desired IdP .
If you selected a default organization role, new users who log in to Atlas using the Login URL have the role you specified.