> This page location: /docs.md > /docs/management.md > /docs/atlas/management/organizations/organization-security.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Configure Federated Authentication

**Note:**

This page applies to both Atlas Infinite and Atlas Core.

MongoDB Federated Authentication links your credentials across MongoDB systems like [MongoDB Support](https://support.mongodb.com/welcome), [MongoDB University](https://learn.mongodb.com/), MongoDB Atlas, MongoDB Cloud Manager, [MongoDB Community Forums](https://community.mongodb.com/), and [MongoDB Feedback](https://feedback.mongodb.com/). Atlas implements authentication using the Federated Identity Management model.

Using the FIM (Federated Identity Management) model:

- Your company manages your credentials using an Identity Provider (IdP (Identity Provider)). With its IdP (Identity Provider), your company can enable you to authenticate with other services across the web.

- You configure MongoDB Atlas to authenticate using data passed from your IdP (Identity Provider).

This goes beyond SSO (Single Sign-On) as your IdP (Identity Provider) manages your credentials, not MongoDB. Your users can use Atlas without needing to remember another username and password.

**Important:**

While you have a federated IdP (Identity Provider) enabled, Atlas disables any other authentication mechanisms.

![SAML Transaction Diagram](/images/SAML_Transaction.svg)

To link your IdP (Identity Provider) to Atlas you provide each with the appropriate metadata. After you link your IdP (Identity Provider) to Atlas, map domains, organizations, and roles to your IdP (Identity Provider):

Domain Mapping

Atlas routes users with email addresses that use [mapped domains](https://www.mongodb.com/docs/atlas/security/manage-domain-mapping.md#std-label-atlas-manage-fed-domain-map) to the associated IdP (Identity Provider).

Organization Mapping

Atlas grants users who log in through the IdP (Identity Provider) access to [mapped Atlas organizations.](https://www.mongodb.com/docs/atlas/security/manage-org-mapping.md#std-label-atlas-manage-fed-org-map)

Role Mapping

As part of the organization mapping, you can choose which [role](https://www.mongodb.com/docs/atlas/reference/user-roles.md#std-label-organization-roles) to grant your users. These roles map to groups in your IdP (Identity Provider).

## Required Access

To manage federated authentication, you must have [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) access to one or more organizations that are delegating federation settings to the instance.

## Federation Management Console

You can manage federated authentication from the Federation
Management Console.

To open the Federation Management console:

1. In Atlas, go to the Federation Management console for your organization.

   If it's not already displayed, select your desired organization from the  Organizations menu in the navigation bar.

   In the sidebar, click Federation under the Identity & Access heading.

   Click Open Federation Management App.

   The [Federation](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Ffederation) page displays.

## Quick Start

If you're configuring single sign-on for users in your organization for the first time, you can follow MongoDB's federation management Quick Start Guide.

To configure single sign-on with the Quick Start Guide:

1. Navigate to the Federation Management App.

   In Atlas, go to the Federation Management console for your organization.

   If it's not already displayed, select your desired organization from the  Organizations menu in the navigation bar.

   In the sidebar, click Federation under the Identity & Access heading.

   Click Open Federation Management App.

   The [Federation](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Ffederation) page displays.

   If it is not already displayed, open the Federation Management console Overview page using the left navigation panel.

   **Note: Federation ID**

   The Overview page displays a **Federation ID**, which is a unique 24-character hexadecimal digit representing a specific federation. This value is distinct for each **federation application**.

2. Click Begin on the Quick Start Guide card.

   The Quick Start Guide walks you through the following:

   1. Adding and verifying your domains.

   2. Configuring your IdP (Identity Provider) with Atlas.

   3. Connecting your domains to your IdP (Identity Provider).

   4. Activating your IdP (Identity Provider) for users to access MongoDB.

   Complete each of the four steps in order.

**Note:**

If you've already completed the federation management Quick Start but want to go through those steps again, click the link at the bottom of the Federation Management console Overview page.

## Tutorials

To configure federated authentication from the Federation
Management console in Atlas, you must:

1. Click Manage Identity Providers and [Link an Identity Provider to Atlas](https://www.mongodb.com/docs/atlas/security/manage-federated-auth.md#std-label-atlas-manage-fed-auth) to ensure that your users are authenticated through your trusted IdP (Identity Provider).

2. Click Manage Domains and [Map Domains to your Identity Provider](https://www.mongodb.com/docs/atlas/security/manage-domain-mapping.md#std-label-atlas-manage-fed-domain-map) to simplify the login experience for users from specified domains. Atlas authenticates users through a mapped IdP (Identity Provider) if their email address matches a mapped domain.

After federating authentication, you can simplify user authorization. In the Federation Management console, click Manage Organizations. You can perform these activities:

1. [Map Atlas organizations](https://www.mongodb.com/docs/atlas/security/manage-org-mapping.md#std-label-atlas-manage-fed-org-map) to your IdP (Identity Provider).

2. [Map Atlas roles](https://www.mongodb.com/docs/atlas/security/manage-role-mapping.md#std-label-atlas-manage-fed-auth-roles) to groups in your IdP (Identity Provider).

End-to-end tutorials on implementing federated authentication:

- [Microsoft Entra ID](https://www.mongodb.com/docs/atlas/security/federated-auth-azure-ad.md#std-label-federated-auth-azure-ad)

- [Google Workspace](https://www.mongodb.com/docs/atlas/security/federated-auth-google-ws.md#std-label-federated-auth-google-ws)

- [Okta](https://www.mongodb.com/docs/atlas/security/federated-auth-okta.md#std-label-federated-auth-okta)

- [PingOne](https://www.mongodb.com/docs/atlas/security/federated-auth-ping-one.md#std-label-federated-auth-ping-one)

## Consideration for Restricted Access to Atlas UI

If you enable [IP access list for the Atlas UI for an organization](https://www.mongodb.com/docs/atlas/tutorial/manage-organizations.md#std-label-atlas-ui-ip-access-list), and restrict access by any user to at least one federated organization, Atlas doesn't allow this user to access the Federation Management console.

## OIDC Setup Guides

For step-by-step instructions on configuring Workforce Identity Federation with OIDC for specific identity providers, see:

- [Configure Workforce Identity Federation from Okta](https://www.mongodb.com/docs/atlas/security/oidc-okta-setup.md#std-label-oidc-okta-setup)

- [Configure Workforce Identity Federation from PingOne](https://www.mongodb.com/docs/atlas/security/oidc-pingone-setup.md#std-label-oidc-pingone-setup)
