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

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

# Manage Identity Providers

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.

The following procedure walks you through linking a SAML (Security Assertion Markup Language) IdP (Identity Provider) to Atlas.

## 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.

## Procedure

**Important: Two-Stage Configuration**

Depending on your Identity Provider, some circular logic may apply when linking it to a Service Provider like Atlas. To link your IdP (Identity Provider) to Atlas:

- Your IdP needs values from Atlas and

- Atlas needs values from your IdP.

To simplify setup, Atlas prompts you to enter placeholder values for the IdP and Atlas configurations. You will replace these values later in the procedure.

### Configure An External Identity Provider Application

To configure Federated Authentication, you must have an external SAML (Security Assertion Markup Language) IdP (Identity Provider) application. In the SAML (Security Assertion Markup Language) IdP (Identity Provider), you must perform the following:

1. Create a new application for Atlas.

2. Configure initial SAML (Security Assertion Markup Language) values for the new application:

   Set placeholder values for the following fields:

   - SP Entity ID or Issuer

   - Audience URI

   - Assertion Consumer Service (ACS) URL

   Set valid values for the following fields:

   | Field | Value |
   | --- | --- |
   | Signature Algorithm | Algorithm used to encrypt the IdP (Identity Provider) signature. Atlas supports the following signature algorithm values: `SHA-1`; `SHA-256` |
   | Name ID | Valid email address. IMPORTANT: Name ID is used as both the email address and the username of your Atlas user account. |
   | Name ID Format | `urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified`; `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` |

   Create attributes with the following Attribute Names for the following SAML Attribute Values:

   | SAML Attribute Name | SAML Attribute Value |
   | --- | --- |
   | `firstName` | First Name |
   | `lastName` | Last Name |
   | `memberOf` | User Groups |

   **Note:**

   The names of these attributes are case sensitive. Type these attribute names as shown in [camelCase.](https://en.wikipedia.org/wiki/Camel_case)

   Save these values.

Once you have completed the initial setup for your IdP (Identity Provider) application, you link the IdP (Identity Provider) to Atlas to federate your users' logins.

### Apply Your Identity Provider to Atlas

**Note: Prerequisite**

This procedure assumes you already have an external IdP (Identity Provider). To learn how to configure an IdP (Identity Provider), see [Configure An External Identity Provider Application.](https://www.mongodb.com/docs/atlas/security/manage-federated-auth.md#std-label-configure-idp-app)

You can configure Federated Authentication in Atlas from the Federation Management Console. Use this console to:

- Configure Identity Providers to authenticate users belonging to specified organizations.

- Connect Atlas Organizations to your IdP (Identity Provider).

- Verify and associate Domains with your IdP (Identity Provider) to force users to authenticate using that IdP.

#### Open the 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.

#### From the Management Console:

1. Click Configure Identity Providers.

2. If you do not have any Identity Providers configured yet, click Setup Identity Provider. Otherwise, on the Identity Providers screen, click Add Identity Provider.

3. Enter or select the following SAML (Security Assertion Markup Language) Protocol Settings.

   | Field | Necessity | Description |
   | --- | --- | --- |
   | Configuration Name | Required | Human-readable label that identifies this configuration. |
   | Configuration Description | Optional | Human-readable label that describes this configuration. |
   | IdP Issuer URI | Required | Identifier for the issuer of the [SAML Assertion.](http://saml.xml.org/assertions) Specify a placeholder value for this field. Obtain the real value for this field from your IdP (Identity Provider) once you have supplied it with the Atlas metadata. |
   | IdP Single Sign-On URL | Required | URL of the receiver of the SAML (Security Assertion Markup Language) AuthNRequest. Specify a placeholder value for this field. Obtain the real value for this field from your IdP (Identity Provider) once you have supplied it with the Atlas metadata. |
   | IdP Signature Certificate | Required | PEM (Privacy Enhanced Mail)-encoded public key certificate of the IdP (Identity Provider). You can obtain this value from your IdP (Identity Provider). You can either: Upload the certificate from your computer, or; Paste the contents of the certificate into a text box. |
   | Request Binding | Required | SAML (Security Assertion Markup Language) Authentication Request Protocol binding used to send the AuthNRequest. Can be either: `HTTP POST`; `HTTP REDIRECT` |
   | Response Signature Algorithm | Required | Response algorithm used to sign the SAML (Security Assertion Markup Language) AuthNRequest. Can be either: `SHA-256`; `SHA-1` |

4. Click Next.

### Configure Your Identity Provider with Atlas Metadata

Having set up your IdP (Identity Provider) in Atlas, you can provide the required Atlas metadata to your IdP (Identity Provider).

1. On the Identity Provider screen in Atlas, click Download metadata to download the metadata required by your IdP (Identity Provider). Atlas provides the data as an `.xml` file.

   ![Image showing how to download metadata](/images/customer-fed-download-metadata-border.png)

   **Note:**

   Atlas provides the Assertion Consumer Service URL and Audience URI if you wish to manually copy and save these values. These values are included in the metadata download.

   **Note:**

   The SAML trust model requires certificate exchange over trusted channels during setup and doesn't require CA-signed certificates. During federated authentication, all traffic between MongoDB Atlas and the browser runs over TLS using a CA-signed certificate. Therefore, `metadata.xml` provides only a self-signed certificate for request signing and signature validation.

2. Upload the metadata to your IdP (Identity Provider).

   You now have the necessary information to replace the placeholder IdP Issuer URI and IdP Single Sign-On URL values set when you set up the initial IdP (Identity Provider) mapping in Atlas.

3. In Atlas, modify the placeholder values set for IdP Issuer URI and IdP Single Sign-On URL for the linked IdP (Identity Provider) with the proper values from your IdP (Identity Provider).

4. Optionally, add a RelayState URL to your IdP (Identity Provider) to send users to a URL you choose and avoid unnecessary redirects after login. You can use:

   | Destination | RelayState URL |
   | --- | --- |
   | MongoDB Atlas | Login URL generated for your identity provider configuration in the Atlas [Federation Management App.](https://www.mongodb.com/docs/atlas/security/federated-authentication.md#std-label-federation-management-access) |
   | MongoDB Support Portal | `https://auth.mongodb.com/app/salesforce/exk1rw00vux0h1iFz297/sso/saml` |
   | MongoDB University | `https://auth.mongodb.com/home/mongodb_thoughtindustriesstaging_1/0oadne22vtcdV5riC297/alndnea8d6SkOGXbS297` |
   | MongoDB Community Forums | `https://auth.mongodb.com/home/mongodbexternal_communityforums_3/0oa3bqf5mlIQvkbmF297/aln3bqgadajdHoymn297` |
   | MongoDB Feedback Engine | `https://auth.mongodb.com/home/mongodbexternal_uservoice_1/0oa27cs0zouYPwgj0297/aln27cvudlhBT7grX297` |
   | MongoDB JIRA | `https://auth.mongodb.com/app/mongodbexternal_mongodbjira_1/exk1s832qkFO3Rqox297/sso/saml` |

5. Return to Atlas and click Finish.

**Important:**

Once you link your IdP (Identity Provider) to Atlas, it shows as Inactive in the Federation Management Console until you [map at least one domain](https://www.mongodb.com/docs/atlas/security/manage-domain-mapping.md#std-label-atlas-manage-fed-domain-map) to the IdP (Identity Provider).

## Next Steps

After you successfully linked your IdP (Identity Provider) to Atlas, you must [map one or more domains to your Identity Provider](https://www.mongodb.com/docs/atlas/security/manage-domain-mapping.md#std-label-atlas-manage-fed-domain-map). Atlas authenticates users from these domains through your IdP (Identity Provider).
