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 must be defined as strings if not specified.
The MongoDB Cloud - Database connector uses the following default correlation and object configurations.
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 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 |
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.