Capabilities

• Sync user identities from MongoDB Atlas to ConductorOne

• Resources supported:

  • Organizations
  • Teams
  • Projects

• Provisioning supported:

  • Team membership
  • Project membership

Add a new MongoDB Atlas connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > Add connector.

2. Search for MongoDB Atlas and click Add.

3. Choose how to set up the new MongoDB Atlas connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

   Do you SSO into MongoDB Atlas using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged MongoDB Atlas app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else. Setting multiple owners is allowed.

   A MongoDB Atlas connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Organization Owner access in MongoDB Atlas

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your MongoDB Atlas connector.

• If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your MongoDB Atlas connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Organization Owner access in MongoDB Atlas must perform this task.

Step 1: Generate an API key in the MongoDB Atlas organization

1. Navigate to the MongoDB Atlas organization you wish to integrate and click Access Manager.

2. Click Create API key.

3. Give the new API key a description, such as “ConductorOne integration”.

4. In the Organization Permissions area, select the relevant permission:

   • Organization Owner if you want to use ConductorOne to provision MongoDB Atlas team and project membership

   • Organization Read Only if you do not want to use ConductorOne for provisioning

5. Click Next.

6. Carefully and copy and save the public key and private key. We’ll use these credentials in Step 2.

Step 2: Add your MongoDB Atlas credentials to ConductorOne

1. In ConductorOne, navigate to the MongoDB Atlas connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > MongoDB Atlas (if there is more than one MongoDB Atlas listed, click the one with your name listed as owner and the status Not connected).

2. Find the Settings area of the page and click Edit.

3. Paste the public key you generated in Step 1 into the Public key field.

4. Paste the private key you generated in Step 1 into the Private key field.

5. Click Save.

6. The connector’s label changes to Syncing, followed by Connected. View the logs to ensure that information is syncing.

That’s it! Your MongoDB Atlas connector is now pulling access data into ConductorOne.

Configure the MongoDB Atlas integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between MongoDB Atlas and ConductorOne.

See the ConductorOne MongoDB Atlas integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.