Provisioning
The MongoDB Cloud - Database 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. |
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.