# SailPoint MongoDB Cloud - Database SaaS Connector Documentation > MongoDB Cloud - Database SaaS Connector Documentation # Documentation # Connecting SailPoint and MongoDB Cloud - Database SaaS To connect SailPoint with MongoDB Cloud - Database, 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 API. 2. Enter the **Public Key** user name for the Atlas API Key with programmatic access. 3. Enter the **Private Key** (password) for the Atlas API Key with programmatic access. 4. Enter the **Project Name** that the connector manages. This field is case-sensitive. A source manages database users from one project. You must configure an additional source to manage a different project's database users. 5. 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**. ## Aggregation Settings Define the scope of the Projects included in your aggregation processes. For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![alt text]()]() To configure your Project scope for aggregation, complete the following: 1. (Optional) In the **Include Project List** field, enter a list of project names to be included during aggregation. After each entry, press Enter to add it to a growing list. For example: - Project1 - Project2 2. (Optional) In the **Exclude Project List** field, enter a list of project names to be excluded during aggregation. After each entry, press Enter to add it to a growing list. For example: - Project1 - Project2 3. 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 - Database 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 - Database 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 - Database SaaS connector supports the following features: > [!NOTE] > > Before you can use any item marked with an asterisk (\*), SailPoint must activate the feature for your site. #### Account Management - Aggregate MongoDB Cloud - Database SaaS users as accounts - \*Provision Accounts - Create, Update - Delete - \*Access Certifications (Certification of entitlements connected to accounts) - \*Password Management #### Account - Group Management - Aggregate MongoDB Cloud database roles as groups To govern access, MongoDB employs Role-Based Access Control (RBAC), where each user is granted one or more roles that determine the user's access to database resources and operations. The MongoDB Cloud - Database SaaS source for SailPoint supports the Role group object for Add and Remove Entitlement operations. For more information on features, refer to [Source Features](). #### Password Management If Password Management is enabled for your organization, you can change the password for a user of the source. After enabling password management on the source, be aware of the following: - The password policy defined in SailPoint applies to accounts on this source. - If you change the password for an application connected to this source, the change will automatically be made to the source itself. For more information on configuring password management, refer to [Password Management Overview](). ## Supported Managed Systems The SailPoint MongoDB Cloud - Database SaaS connector supports MongoDB Databases on MongoDB Atlas Cloud. ## Prerequisites - MongoDB Atlas (where the MongoDB database resides) 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 the data. For more information, refer to [IP Address Allow List]() in the SailPoint Developer Community documentation. - An Atlas API key is required to grant programmatic access to the MongoDB project. This Atlas API key acts as the service account and it is used to manage database users in each Project under a single Organization, where the following permissions are required: | Operation | Permission | | --- | --- | | Test Connection | Organization Member
Project Read Only | | Account Aggregation | Organization Member
Project Read Only | | Entitlement Aggregation | Organization Member
Project Read Only | | Create | Organization Member
Project Owner | | Update | Organization Member
Project Owner | | Add/Remove Entitlement | Organization Member
Project Owner | # Provisioning The MongoDB Cloud - Database SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in MongoDB Cloud - Database directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes | Account Attribute | Generator | Description | | --- | --- | --- | | Database Name\* | Static | The database used to authenticate the user:
\- Database Name must be `admin` for Password Authentication and LDAP Authentication, where **LDAP Auth Type** is `GROUP`.
\- Database Name must be `$external` for X.509 Authentication and LDAP Authentication, where **LDAP Auth Type** is `USER`.
\- Database Name must be `admin` for **SCRAM Auth Type**. | | Username\* | Create Unique Account ID | The username used for authentication. | | Authentication Method | Static | The authentication method supported by MongoDB Cloud managed system. The expected values are:
\- Password Authentication
\- X.509 Authentication
\- LDAP Authentication | | Password | Create Password | The password associated with the specified username | | X509 Type | Disable | The authentication type using the X.509 certificate. The expected values are:
\- MANAGED
\- CUSTOMER | | LDAP Auth Type | Disable | The authentication type using the LDAP credentials. The expected values are:
\- USER
\- GROUP | | Delete After Date | Disable | ISO-8601-formatted UTC date after which point Atlas MongoDB deletes a temporary user. You can't set this parameter for a permanent user.

**Note**: This is not applicable for the X.509 Auth Type user, because a X.509 Auth type temporary user cannot be created.

The date format is `YYYY-MM-DDThh:mm:ssZ`. For example, you can use `2020-01-01T08:06:48Z`. You may include an ISO-8601 time zone designator to ensure that the delete-after date occurs with respect to the user's configured local time zone.

The date you specify must be in the future and within one week of the time when you make the API request. | # 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 - Database 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 - Database SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | Username | Equals | Username | ## 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 | | --- | --- | | Username | Account | | Native Identity | Group | ### Default Account Attributes The MongoDB Cloud - Database 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 | | --- | --- | | Database Name | Name of the database | | Labels | Key-value pairs that tag and categorize the database user | | LDAP Auth Type | Describes the type of LDAP authentication | | Username | Username for authentication. This is an Account ID which must not be changed. | | Delete After Date | ISO-8601-formatted UTC date after which point Atlas MongoDB deletes a temporary user. You can't set this parameter for a permanent user. The date format is `YYYY-MM-DDThh:mm:ssZ`. For example, `2021-04-18T03:28:17+00:00`. You may include an ISO-8601 time zone designator to ensure that the delete-after date occurs with respect to the user's configured local time zone. | | X509 Type | Describes the type of X509 authentication | | Roles | Collections on which the Roles apply | # 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 displays during a Test Connection operation: ```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 [Prerequisites]() are met. The following error displays during a Test Connection operation: ```javascript {"reason": , "Unauthorized" "error": 401, "detail": }"You are not authorized for this resource. ``` **Resolution** - Ensure that the service account has the required permissions. ## Entitlement Error The following error displays during an Add Entitlement operation: ```javascript {"detail": "Duplicate database roles specified for user user2: atlasAdmin.", "error": 400, "errorCode": "DUPLICATE_DATABASE_ROLES", "parameters": ["user2", "atlasAdmin"], "reason": "Bad Request"} ``` **Resolution** - This is because a duplicate role is assigned to a database user. Ensure that different roles are assigned to database users. ## Aggregation/Provisioning Error The following error displays during an Aggregation or Provisioning operation: ```javascript Invalid project name specified or service account does not have sufficient privileges on the project name specified ``` **Resolution** - Ensure that Project Name is correct, or service account has sufficient privileges.