Set up a MongoDB Atlas connector
Capabilities
Resource | Sync | Provision |
---|---|---|
Accounts | ✅ | |
Organizations | ✅ | |
Teams | ✅ | ✅ |
Projects | ✅ | ✅ |
Available hosting methods
Choose the hosting method that best suits your needs:
Method | Availability | Notes |
---|---|---|
Cloud-hosted | ✅ | A built-in, no-code connector hosted by ConductorOne. |
Self-hosted | ✅ | The MongoDB connector, hosted and run in your own environment. |
Gather MongoDB Atlas credentials
Each setup method requires you to pass in credentials generated in MongoDB Atlas. Gather these credentials before you move on.
A user with Organization Owner access in MongoDB Atlas must perform this task.
Generate an API key in the MongoDB Atlas organization
Navigate to the MongoDB Atlas organization you wish to integrate and click Access Manager.
Click Create API key.
Give the new API key a description, such as “ConductorOne integration”.
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
Click Next.
Carefully and copy and save the public key and private key.
That’s it! Next, move on to the instructions for your chosen setup method.
Set up a MongoDB Atlas cloud-hosted connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of MongoDB Atlas credentials generated by following the instructions above
In ConductorOne, click Connectors > Add connector.
Search for MongoDB Atlas and click Add.
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
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Paste the public key into the Public key field.
Paste the private key into the Private key field.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your MongoDB Atlas connector is now pulling access data into ConductorOne.
Set up a MongoDB Atlas cloud-hosted connector using Terraform
As an alternative to the cloud-hosted setup 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.
Set up a MongoDB Atlas self-hosted connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of MongoDB Atlas credentials generated by following the instructions above
When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.
Step 1: Configure the MongoDB Atlas connector
In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
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
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.
Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your MongoDB Atlas connector deployment:
Secrets configuration
# baton-mongodb-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-mongodb-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID: <ConductorOne client ID>
BATON_CLIENT_SECRET: <ConductorOne client secret>
# MongoDB Atlas credentials
BATON_PRIVATE_KEY: <MongoDB private key>
BATON_PUBLIC_KEY: <MongoDB public key>
# Optional: include if you want ConductorOne to provision access using this connector
BATON_PROVISIONING: true
See the connector’s README or run
--help
to see all available configuration flags and environment variables.
Deployment configuration
# baton-mongodb.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-mongodb
labels:
app: baton-mongodb
spec:
selector:
matchLabels:
app: baton-mongodb
template:
metadata:
labels:
app: baton-mongodb
baton: true
baton-app: mongodb
spec:
containers:
- name: baton-mongodb
image: ghcr.io/conductorone/baton-mongodb:latest
args: ["service"]
imagePullPolicy: IfNotPresent
envFrom:
- secretRef:
name: baton-mongodb-secrets
Step 3: Deploy the connector
Create a namespace in which to run ConductorOne connectors (if desired):
kubectl create namespace conductorone
Apply the secret configuration:
kubectl -n conductorone apply -f baton-mongodb-secrets.yaml
Apply the deployment:
kubectl -n conductorone apply -f baton-mongodb.yaml
Step 4: Verify the deployment
Check that the deployment is running:
kubectl -n conductorone get pods
View the connector logs:
kubectl -n conductorone logs -l app=baton-${baton-mongodb}
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the MongoDB Atlas connector to. MongoDB Atlas data should be found on the Entitlements and Accounts tabs.
That’s it! Your MongoDB Atlas connector is now pulling access data into ConductorOne.