# SailPoint MongoDB Cloud - Atlas SaaS Connector Documentation > MongoDB Cloud - Atlas SaaS Connector Documentation # Documentation # Connecting SailPoint and MongoDB Cloud - Atlas SaaS To connect SailPoint with MongoDB Cloud - Atlas, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings Provide the information required to connect and interact with the source. > [!NOTE] > > **Screenshot** > > [![alt text]()]() To configure connection settings, complete the following: 1. Enter the **API URL** for the Atlas SaaS API. 2. Enter the **Public Key** username for the Atlas SaaS API Key with programmatic access. 3. Enter the **Private Key** (password) for the Atlas SaaS API Key with programmatic access. 4. Select **Save**. ## Activity Insights Settings SailPoint pulls in activity data in the form of events like user logins, password changes, and content updates within the application. You can view an identity’s activity data within an application to discover trends for that user. > [!IMPORTANT] > > Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on utilizing activity data, refer to [Activity Insights](). Activity Insights Settings allows you to gather account information and activity data from MongoDB Cloud - Atlas. To enable Activity Insights for the MongoDB Cloud - Atlas application, refer to [Prerequisites]() for more information. To configure Activity Insights, complete the following: > [!NOTE] > > **Screenshot** > > [![Activity Insights Settings]()]() 1. Go to **Activity Insights Settings**. 2. Select **Enable Activity Insights** to view access to data insights on source and application activity such as logins and other app-specific events. 3. Select **Save**. ## Additional Settings > [!NOTE] > > **Screenshot** > > [![alt text]()]() Use the Additional Settings tab to configure optional settings, such as the page size and connection timeout. ### Page Size The page size defines the number of objects to fetch per page, when iterating over large numbers of objects. The default is 100. To configure the page size: 1. In the **Page Size** enter the desired value for the page size. 2. Select **Save**. ### Connection Timeout The connection timeout defines the amount of time allowed for a connection to be established. If a connection is not established within this time duration, the connector fails the connection. The default is 1 minute. 1. In the **Connection Timeout (in Minutes)** field, enter the desired value for the connection timeout in minutes. 2. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with MongoDB Cloud - Atlas SaaS This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of a MongoDB Cloud - Atlas SaaS connector. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The SailPoint MongoDB Cloud - Atlas SaaS connector supports the following features: - Aggregation of active MongoDB Cloud - Atlas SaaS users as accounts - Add and remove entitlements for Role group objects - Entitlement aggregation operations for Role group objects For more information on supported features, refer to [Source Features](). ### Revocation of Project Roles If you revoke all project roles from an Atlas SaaS User, then the user is deleted from one project or multiple projects based on the selection of roles for revocation. Note that roles may belong to one project or multiple projects. While removing Organization roles from a user, at least one Organization role must be kept as assigned. ### Activity Insights Activity Insights supports activity from the MongoDB Cloud - Atlas SaaS source and its associated accounts. This enables you to gather account information and activity data from the MongoDB Cloud - Atlas SaaS source. > [!IMPORTANT] > > Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on configuring Activity Insights, refer to [Activity Insights](). ## Supported Managed Systems The MongoDB Cloud - Atlas SaaS connector supports the MongoDB Atlas SaaS Cloud source. ## Prerequisites - MongoDB Atlas SaaS can only connect from a trusted IP address. Within Atlas, you must create a list of trusted IP addresses that can be used to connect to a source and access data. For more information, refer to [IP Address Allow List]() in the SailPoint Developer Community documentation. - An Atlas SaaS API key is required to grant programmatic access to the MongoDB Project. This Atlas SaaS API key acts as the service account and is used to manage database users in each Project under a single Organization. The following permissions are required: | Operation | Permission | | --- | --- | | Test Connection | Organization member
Project Read Only (For projects required to be managed) | | Account Aggregation | Organization member
Project Read Only (For projects required to be managed) | | Entitlement Aggregation | Organization member
Project Read Only (For projects required to be managed) | | Add/Remove Entitlement | Organization Owner | > **Note** > > If the list of managed Projects is long, assign *Organization Read Only* access instead of *Project Read Only* access for all Projects. This applies for Test Connection, Account Aggregation, and Group Aggregation processes. # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The MongoDB Cloud - Atlas SaaS connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the MongoDB Cloud - Atlas SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | Email Address | Equals | Work Email | | Username | Equals | Username | | Display Name | Equals | Name | ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account ID SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*. > [!CAUTION] > > Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts. > > To resolve issues caused by changing account IDs, reconfigure them to their default values. The following table lists the default account IDs for this connector: | Account ID | Schema Object Type | | --- | --- | | Id | Account | | Native Identity | Role | ### Default Account Attributes The MongoDB Cloud - Atlas SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. | Attribute Name | Description | | --- | --- | | Display Name | The user's display name | | Username | Username for authentication | | Id | A unique identifier for the Organization API Key or Atlas SaaS User. This is an Account ID which must not be changed. | | First Name | The user's first name / given name | | Last Name | The user's last name / family name | | Mobile Number | The user's mobile number | | Email Address | The user's email address | | Country | The user's country code | | Roles | Roles assigned to the user | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](). ## Test Connection Errors The following error message displays during the Test Connection operations: ```javascript {"detail":"IP address 103.93.47.143 is not allowed to access this resource.","error":403,"errorCode":"IP_ADDRESS_NOT_ON_WHITELIST","parameters":["103.93.47.143"],"reason":"Forbidden"} ``` **Resolution** - Ensure that all the [Prerequisites]() are met, and that all the VA's IP addresses configured for the MongoDB Cloud - Atlas SaaS source are in the list of trusted IPs on the managed system. ## Entitlement Errors The following error message displays during Add/Remove Entitlement operations: ```javascript {"detail":"The currently logged in user does not have the user administrator role for any group, team, or organization containing user 5ed60bdb5e57f641091cf871.","error":401,"errorCode":"NOT_USER_ADMIN","parameters":["5ed60bdb5e57f641091cf871"],"reason":"Unauthorized"} ``` **Resolution** - Verify that the service account has sufficient permissions. The following error displays during Remove Entitlement operations: ```javascript Cannot demote the last owner of the group. ``` **Resolution** - Ensure that you have assigned at least one Project Owner. ## Revoking All Organization Roles Fails The following error message displays when revoking all organization roles: ```javascript Cannot remove all roles from the Atlas SaaS user. ``` **Resolution** - Ensure that you are not deleting all the organization roles.