On this Page

This account is used by the Snaps in the MongoDB Snap Pack.

Account Configuration

In SnapLogic, you can create accounts either for projects or in shared folders.

To create a MongoDB account:

Click on the project or shared folder for which you want to create the account. This displays a page that displays all the resources associated with the project or folder.
Click Create > MongoDB, and then choose the MongoDB Account you want to create.
- Select MongoDB Account to connect to a single node.
- Select Replica Set Account to connect to replica sets for operations. For more information on replication in MongoDB, see the Replication page in MongoDB documentation.
  
  To add an account for MongoDB Atlas, you must configure an account as either Replica Set or Replica Set Dynamic Account because MongoDB Atlas starts with a replica set of 3 nodes. Read more on connecting MongoDB Atlas via drivers.
Supply a Label for the account.
Supply the necessary information for the appropriate account type:
- MongoDB Account
- Replica Set Account
- MongoDB Dynamic Account
- Replica Set Dynamic Account
  
  For detailed guidance on setting up each of these accounts, see the Account Types section below.
Supply additional information on this account in the Notes field of the Info tab.

Account Types

MongoDB Account

Account Settings

Label	Required. User provided label for the account instance. Default value: [None]
Hostname	Required. MongoDB Hostname Default value: [None]
Port	Required. The MongoDB Port. Default value: [None]
Database name	The database that the MongoDB account is defined in. This is also the default database used for queries. Ensure to provide the database name when selecting the TLS/SSL option in the Encryption type property. Default value: [None]
Username	Required. The MongoDB Username. Default value: [None]
Password	Required. The password associated with the MongoDB Username. Default value: [None]
Authentication type	Required. The authentication type that you want to use with this account. The options available are: Default: No authentication LDAP: Username/password retrieved from the configured LDAP server. LDAP Proxy Authentication You must configure the MongoDB server to access the LDAP authentication mechanism. Click here to know more about configuring the service. Plain: The username and password combination provided by your administrator. X.509 (Digital Certificates): Issued by a certificate authority; or self-signed. Using X.509 Digital Certificates The X.509 certificate uses the international X.509 public key infrastructure (PKI) standard to check whether a public key belongs to the declared user, computer, or service identity listed in the certificate. In SnapLogic, the X.509 Digital Certificates authentication type enables you to use digital certificates to authenticate your requests with MongoDB. For more details on X.509 digital certificates, see Using x.509 Certificates to Authenticate Clients. To use X.509 digital certificates: Enter data in the Label, Hostname, Port, and Database Name fields as appropriate. In the Username field, enter the Distinguished Name (DN) of the certificate in the keystore from where you retrieved it. Example: CN=admin,OU=JSDev,O=Jaspersoft,L=San Francisco,ST=CA,C=US There are many ways of presenting the DN as a string, so the format seen in other tools may not be appropriate here. For example, most formats use '/' instead of ',' as separators. Leave the Password field blank. Select the Authentication Type as X.509 (Digital Certificates). Set the Encryption Type to ssl certs. Update the SSL Certs Properties section as follows: Enter the location of the trust store in the Truststore Filepath field. The trust store must contain trusted certificates from the certificate authorities (CAs) that signed both the Mongo server and client certificates. It's a good practice for the truststore to include the Mongo server's certificate as well; but it's not mandatory, since the client can validate the certificate via the CA certificate. Enter the Truststore Password in the field provided. Enter the location of the keystore in the Keystore Filepath field. The keystore must contain the certificate and key with the same DN as used in the Username field. Again, as in the case of the Distinguished Name, the formats used may appear to be different. The keystore may also need to include the certificate chain (the list of SSL certificates, right from the root certificate to the end-user certificate) for the client's cert. Enter the Keystore File Password in the field provided. Click Validate to check your settings; click Apply to save your changes and exit the popup once validation succeeds. Default value: Default
Encryption type	Required. The encryption type for connecting Mongo instance. The options available are None, TLS/SSL and SSL certs If None is selected, data is not encrypted. If TLS/SSL is selected, data is encrypted without certificate validation. Ensure to provide the database name in the Database name property to validate the user against that particular database name. If SSL certs is Selected, the data is encrypted ensuring the certificate validation. Default value: None
SSL certs properties	Conditional. Configure the keystore and truststore properties only when the encryption type is selected as "SSL certs". This ensures the validation of the certificate.
Truststore filepath	The location of the trust store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://... Example: shared/cacert_keystore.p12 Default value: [None]
Truststore password	Truststorepassword to access the truststore file of the server.
Keystore filepath	The location of the key store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://... Example: shared/client_keystore.p12 Default value: [None]
Keystore file password	Keystore password to access the keystore file of the client.
Connection properties	Configure the connection properties to specify connection and server selection timeouts.
Connection timeout (seconds)	The number of seconds the Mongo driver waits before aborting a new connection attempt. For example, if you set the Connection timeout limit to 30 seconds, and the Snap fails to establish a connection in 30 seconds, the pipeline logs a timeout exception and aborts execution. A value of 0 seconds specifies an infinite timeout. Default value: 10
Server Selection timeout (seconds)	The number of seconds the Mongo driver waits to select a server for an operation before aborting the selection. For example, if you set the Server Selection timeout to 30 seconds, and the Snap fails to find a server until 30 seconds, the pipeline logs an error and aborts execution. A value of 0 seconds specifies an infinite timeout. Default value: 30
MongoDB cursor properties	Use this field set to configure the MongoDB cursor timeout properties. This field set contains the Use Cursor Timeout field.
Use Cursor Timeout	Select this checkbox to set a timeout for idle cursors, which means, it enables the server to close a cursor automatically after a period of inactivity. This option allows you to connect to Atlas Free Tier database and Shared Clusters using the MongoDB accounts. Refer to Atlas Free Tier limitations for more information. For all the existing Mongo DB accounts, the Use Cursor Timeout check box is deselected by default. Default value: Not Selected

Account Encryption

Standard Encryption	If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.
Enhanced Encryption	If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account. Account: High: Password Medium + High: Username, password Low + Medium + High: Username, password, hostname, database name

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account.

Account:

High: Password
Medium + High: Username, password
Low + Medium + High: Username, password, hostname, database name

Replica Set Account

Account Settings

Label

Required. User provided label for the account instance.

Default value: [None]

Replica Set Configuration

Required. Hostnames and ports for MongoDB replica set.

Default value: [None]

Hostname

The MongoDB Hostname
Default value: [None]

Port

The MongoDB port.

Default value: [None]

Database name

Required. The database that the MongoDB account is defined in. This is also the default database used for queries.

Default value: None

To validate a MongoDB Atlas account, enter the name as admin. Alternatively, to override the actual database name in the Database name property at the Snap settings level.

Username

Required. MongoDB Username

Default value: [None]

Password

Required. The password associated with the MongoDB Username.

Default value: [None]

Authentication type

Required. The authentication type that you want to use with this account. The options available are:

Default: No authentication

To validate a MongoDB Atlas account, select Default.
LDAP: Username/password retrieved from the configured LDAP server. LDAP Proxy Authentication

You must configure the MongoDB server to access the LDAP authentication mechanism. Click here to know more about configuring the service.
Plain: The username and password combination provided by your administrator.
X.509 (Digital Certificates): Issued by a certificate authority; or self-signed.
Using X.509 Digital Certificates
The X.509 certificate uses the international X.509 public key infrastructure (PKI) standard to check whether a public key belongs to the declared user, computer, or service identity listed in the certificate. In SnapLogic, the X.509 Digital Certificates authentication type enables you to use digital certificates to authenticate your requests with MongoDB. For more details on X.509 digital certificates, see Using x.509 Certificates to Authenticate Clients.
To use X.509 digital certificates:
1. Enter data in the Label, Hostname, Port, and Database Name fields as appropriate.
2. In the Username field, enter the Distinguished Name (DN) of the certificate in the keystore from where you retrieved it.
  Example: CN=admin,OU=JSDev,O=Jaspersoft,L=San Francisco,ST=CA,C=US
  
  There are many ways of presenting the DN as a string, so the format seen in other tools may not be appropriate here. For example, most formats use '/' instead of ',' as separators.
3. Leave the Password field blank.
4. Select the Authentication Type as X.509 (Digital Certificates).
5. Set the Encryption Type to ssl certs.
6. Update the SSL Certs Properties section as follows:
  1. Enter the location of the trust store in the Truststore Filepath field. The trust store must contain trusted certificates from the certificate authorities (CAs) that signed both the Mongo server and client certificates.
    It's a good practice for the truststore to include the Mongo server's certificate as well; but it's not mandatory, since the client can validate the certificate via the CA certificate.
  2. Enter the Truststore Password in the field provided.
  3. Enter the location of the keystore in the Keystore Filepath field. The keystore must contain the certificate and key with the same DN as used in the Username field. Again, as in the case of the Distinguished Name, the formats used may appear to be different. The keystore may also need to include the certificate chain (the list of SSL certificates, right from the root certificate to the end-user certificate) for the client's cert.
  4. Enter the Keystore File Password in the field provided.
7. Click Validate to check your settings; click Apply to save your changes and exit the popup once validation succeeds.

Default value: Default

Encryption type

Required. The encryption type for connecting Mongo instance. The options available are None, TLS/SSL and SSL certs

If None is selected, data is not encrypted.

If TLS/SSL is selected, data is encrypted without certificate validation.

If SSL certs is Selected, the data is encrypted ensuring the certificate validation.

Default value: None

To validate a MongoDB Atlas account, select TLS/SSL.

SSL certs properties

Conditional. Configure the keystore and truststore properties only when the encryption type is selected as "SSL certs". This ensures the validation of the certificate.

Truststore filepath

The location of the trust store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://...

Example: shared/cacert_keystore.p12
Default value: [None]

Truststore password

Truststorepassword to access the truststore file of the server.

Keystore filepath

The location of the key store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://...

Example: shared/client_keystore.p12
Default value: [None]

Keystore file password

Keystore password to access the keystore file of the client.

Connection properties

Configure the connection properties to specify connection and server selection timeouts.

Connection timeout (seconds)

The number of seconds the Mongo driver waits before aborting a new connection attempt.
For example, if you set the Connection timeout limit to 30 seconds, and the Snap fails to establish a connection in 30 seconds, the pipeline logs a timeout exception and aborts execution.

A value of 0 seconds specifies an infinite timeout.

Default value: 10

Server Selection timeout (seconds)

The number of seconds the Mongo driver waits to select a server for an operation before aborting the selection.

For example, if you set the Server Selection timeout to 30 seconds, and the Snap fails to find a server until 30 seconds, the pipeline logs an error and aborts execution.

A value of 0 seconds specifies an infinite timeout.

Default value: 30

MongoDB cursor properties

Use this field set to configure the MongoDB cursor timeout properties.
This field set contains the Use Cursor Timeout field.

Use cursor timeout

Select this checkbox to set a timeout for idle cursors, which means, it enables the server to close a cursor automatically after a period of inactivity.

This option allows you to connect to Atlas Free Tier database and Shared Clusters using the MongoDB accounts. Refer to Atlas Free Tier limitations for more information.

For all the existing Mongo DB accounts, the Use Cursor Timeout check box is deselected by default.

Default value: Not Selected

Read preference

Choose an option to define read preference options when querying data. Available options are:

Primary
Primary preferred
Secondary
Secondary preferred
Nearest

Default value: Primary

Account Encryption

Standard Encryption	If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.
Enhanced Encryption	If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account. Account: High: Password Medium + High: Username, Password Low + Medium + High: Hostname, Database name, Username, Password

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account.

Account:

High: Password
Medium + High: Username, Password
Low + Medium + High: Hostname, Database name, Username, Password

MongoDB Dynamic Account

Account Settings

Expression-enabled authentication fields, such as Username, Password, and Client Secret, support Secrets Management, a SnapLogic add-on that allows you to store endpoint credentials in a third-party secrets manager, such as AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. During validation and execution, pipelines obtain the credentials directly from the secrets manager. Learn more: Configure Accounts to use secrets.

Label	Required. User provided label for the account instance. Default value: [None]
Hostname	Required. The MongoDB Hostname. Enable the expression property to use a pipeline parameter. Default value: [None]
Port	Required. The MongoDB port. Enable the expression property to use a pipeline parameter. Default value: [None]
Database name	Required. The database that the MongoDB account is defined in. This is also the default database used for queries. Enable the expression property to use a pipeline parameter. Example: _dbName Default value: [None]
Username	Required. MongoDB Username Enable the expression property to use a pipeline parameter. Default value: [None]
Password	Required. The password associated with the MongoDB Username Enable the expression property to use a pipeline parameter. Default value: [None]
Authentication type	Required. The authentication type that you want to use with this account. The options available are: Default: No authentication LDAP: Username/password retrieved from the configured LDAP server. LDAP Proxy Authentication You must configure the MongoDB server to access the LDAP authentication mechanism. Click here to know more about configuring the service. Plain: The username and password combination provided by your administrator. X.509 (Digital Certificates): Issued by a certificate authority; or self-signed. Using X.509 Digital Certificates The X.509 certificate uses the international X.509 public key infrastructure (PKI) standard to check whether a public key belongs to the declared user, computer, or service identity listed in the certificate. In SnapLogic, the X.509 Digital Certificates authentication type enables you to use digital certificates to authenticate your requests with MongoDB. For more details on X.509 digital certificates, see Using x.509 Certificates to Authenticate Clients. To use X.509 digital certificates: Enter data in the Label, Hostname, Port, and Database Name fields as appropriate. In the Username field, enter the Distinguished Name (DN) of the certificate in the keystore from where you retrieved it. Example: CN=admin,OU=JSDev,O=Jaspersoft,L=San Francisco,ST=CA,C=US There are many ways of presenting the DN as a string, so the format seen in other tools may not be appropriate here. For example, most formats use '/' instead of ',' as separators. Leave the Password field blank. Select the Authentication Type as X.509 (Digital Certificates). Set the Encryption Type to ssl certs. Update the SSL Certs Properties section as follows: Enter the location of the trust store in the Truststore Filepath field. The trust store must contain trusted certificates from the certificate authorities (CAs) that signed both the Mongo server and client certificates. It's a good practice for the truststore to include the Mongo server's certificate as well; but it's not mandatory, since the client can validate the certificate via the CA certificate. Enter the Truststore Password in the field provided. Enter the location of the keystore in the Keystore Filepath field. The keystore must contain the certificate and key with the same DN as used in the Username field. Again, as in the case of the Distinguished Name, the formats used may appear to be different. The keystore may also need to include the certificate chain (the list of SSL certificates, right from the root certificate to the end-user certificate) for the client's cert. Enter the Keystore File Password in the field provided. Click Validate to check your settings; click Apply to save your changes and exit the popup once validation succeeds. Default value: Default
Encryption type	Required. The encryption type for connecting Mongo instance. The options available are None, TLS/SSL and SSL certs If None is selected, data is not encrypted. If TLS/SSL is selected, data is encrypted without certificate validation. If SSL certs is Selected, the data is encrypted ensuring the certificate validation. Default value: None
SSL certs properties	Conditional. Configure the keystore and truststore properties only when the encryption type is selected as "SSL certs". This ensures the validation of the certificate.
Truststore filepath	The location of the trust store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://... Example: shared/cacert_keystore.p12 Default value: [None]
Truststore password	Truststorepassword to access the truststore file of the server.
Keystore filepath	The location of the key store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://... Example: shared/client_keystore.p12 Default value: [None]
Keystore file password	Keystore password to access the keystore file of the client.
Connection properties	Configure the connection properties to specify connection and server selection timeouts.
Connection timeout (seconds)	The number of seconds the Mongo driver waits before aborting a new connection attempt. For example, if you set the Connection timeout limit to 30 seconds, and the Snap fails to establish a connection in 30 seconds, the pipeline logs a timeout exception and aborts execution. A value of 0 seconds specifies an infinite timeout. Default value: 10
Server Selection timeout (seconds)	The number of seconds the Mongo driver waits to select a server for an operation before aborting the selection. For example, if you set the Server Selection timeout to 30 seconds, and the Snap fails to find a server until 30 seconds, the pipeline logs an error and aborts execution. A value of 0 seconds specifies an infinite timeout. Default value: 30
MongoDB cursor properties	Use this field set to configure the MongoDB cursor timeout properties. This field set contains the Use Cursor Timeout field.
Use cursor timeout	Select this checkbox to set a timeout for idle cursors, which means, it enables the server to close a cursor automatically after a period of inactivity. This option allows you to connect to Atlas Free Tier database and Shared Clusters using the MongoDB accounts. Refer to Atlas Free Tier limitations for more information. For all the existing Mongo DB accounts, the Use Cursor Timeout check box is deselected by default. Default value: Not Selected

Account Encryption

Standard Encryption	If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.
Enhanced Encryption	If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account. Account: High: Password Medium + High: Username, Password Low + Medium + High: Username, Password, Hostname, Database name

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

High: Password
Medium + High: Username, Password
Low + Medium + High: Username, Password, Hostname, Database name

Example

Setting a MongoDB Dynamic Account

Selecting the Dynamic Account allows the users to pass the account details dynamically as a pipeline parameter. This would enable the users to use the same Snap within a pipeline to connect to different database instances.

For the pipeline, define the pipeline parameters:

hostname
database
username
password
port

You will supply values for them in the Dynamic Account.

In DynamoDB - Update pipeline, create a DynamoDB Dynamic Account (In this pipeline the MongoDB Update Snap is updating the documents on a MongoDB collection in a JSON format using the JSON Generator Snap).

Set the expression toggle on for the properties you want to pass the values dynamically.
Set Hostname to _hostname, Port to _port, Database Name to _database, Username to _username, and Password to _password.
Click Apply and fill the Snap Settings for the desired function.

You cannot Validate an account connection when creating a MongoDB Dynamic Account because the account properties of a dynamic account are provided dynamically as pipeline parameters.

Replica Set Dynamic Account

Account Settings

Label

User provided label for the account instance

Replica Set Configuration

Hostnames and ports for MongoDB replica set.

Default value: [None]

Hostname

The MongoDB Hostname.

Default value: [None]

Port

The MongoDB port.

Default value: [None]

Database name

The database that the MongoDB account is defined in. This is also the default database used for queries.

Enable the expression property to use a pipeline parameter.

Example: _dbName

Default value: None

To validate a MongoDB Atlas account, enter the name as admin. Alternatively, to override the actual database name in the Database name property at the Snap settings level.

Username

The MongoDB Username.

Enable the expression property to use a pipeline parameter.

Example: _username

Default value: [None]

Password

The password associated with the MongoDB Username.
Enable the expression property to use a pipeline parameter.

Example: _password

Default value: [None]

Authentication type

Required. The authentication type that you want to use with this account. The options available are:

Default: No authentication

To validate a MongoDB Atlas account, select Default.
LDAP: Username/password retrieved from the configured LDAP server. LDAP Proxy Authentication

You must configure the MongoDB server to access the LDAP authentication mechanism. Click here to know more about configuring the service.
Plain: The username and password combination provided by your administrator.
X.509 (Digital Certificates): Issued by a certificate authority; or self-signed.
Using X.509 Digital Certificates
The X.509 certificate uses the international X.509 public key infrastructure (PKI) standard to check whether a public key belongs to the declared user, computer, or service identity listed in the certificate. In SnapLogic, the X.509 Digital Certificates authentication type enables you to use digital certificates to authenticate your requests with MongoDB. For more details on X.509 digital certificates, see Using x.509 Certificates to Authenticate Clients.
To use X.509 digital certificates:
1. Enter data in the Label, Hostname, Port, and Database Name fields as appropriate.
2. In the Username field, enter the Distinguished Name (DN) of the certificate in the keystore from where you retrieved it.
  Example: CN=admin,OU=JSDev,O=Jaspersoft,L=San Francisco,ST=CA,C=US
  
  There are many ways of presenting the DN as a string, so the format seen in other tools may not be appropriate here. For example, most formats use '/' instead of ',' as separators.
3. Leave the Password field blank.
4. Select the Authentication Type as X.509 (Digital Certificates).
5. Set the Encryption Type to ssl certs.
6. Update the SSL Certs Properties section as follows:
  1. Enter the location of the trust store in the Truststore Filepath field. The trust store must contain trusted certificates from the certificate authorities (CAs) that signed both the Mongo server and client certificates.
    It's a good practice for the truststore to include the Mongo server's certificate as well; but it's not mandatory, since the client can validate the certificate via the CA certificate.
  2. Enter the Truststore Password in the field provided.
  3. Enter the location of the keystore in the Keystore Filepath field. The keystore must contain the certificate and key with the same DN as used in the Username field. Again, as in the case of the Distinguished Name, the formats used may appear to be different. The keystore may also need to include the certificate chain (the list of SSL certificates, right from the root certificate to the end-user certificate) for the client's cert.
  4. Enter the Keystore File Password in the field provided.
7. Click Validate to check your settings; click Apply to save your changes and exit the popup once validation succeeds.

Default value: Default

Encryption type

Required. The encryption type for connecting Mongo instance. The options available are None, TLS/SSL and SSL certs

If None is selected, data is not encrypted.

If TLS/SSL is selected, data is encrypted without certificate validation.

If SSL certs is Selected, the data is encrypted ensuring the certificate validation.

Default value: None

To validate a MongoDB Atlas account, select TLS/SSL.

SSL certs properties

Conditional. Configure the keystore and truststore properties only when the encryption type is selected as "SSL certs". This ensures the validation of the certificate.

Truststore filepath

The location of the trust store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://...

Example: shared/cacert_keystore.p12
Default value: [None]

Truststore password

Truststorepassword to access the truststore file of the server.

Keystore filepath

The location of the key store file in PKCS#12 format, can be in SLDB or any other unauthenticated endpoint such as https://...

Example: shared/client_keystore.p12
Default value: [None]

Keystore file password

Keystore password to access the keystore file of the client.

Connection properties

Configure the connection properties to specify connection and server selection timeouts.

Connection timeout (seconds)

The number of seconds the Mongo driver waits before aborting a new connection attempt.

For example, if you set the Connection timeout limit to 30 seconds, and the Snap fails to establish a connection in 30 seconds, the pipeline logs a timeout exception and aborts execution.

A value of 0 seconds specifies an infinite timeout.

Default value: 10

Server Selection timeout (seconds)

The number of seconds the Mongo driver waits to select a server for an operation before aborting the selection.

For example, if you set the Server Selection timeout to 30 seconds, and the Snap fails to find a server until 30 seconds, the pipeline logs an error and aborts execution.

A value of 0 seconds specifies an infinite timeout.

Default value: 30

MongoDB cursor properties

Use this field set to configure the MongoDB cursor timeout properties.
This field set contains the Use Cursor Timeout field.

Use cursor timeout

Select this checkbox to set a timeout for idle cursors, which means, it enables the server to close a cursor automatically after a period of inactivity.

This option allows you to connect to Atlas Free Tier database and Shared Clusters using the MongoDB accounts. Refer to Atlas Free Tier limitations for more information.

For all the existing Mongo DB accounts, the Use Cursor Timeout check box is deselected by default.

Default value: Not Selected

Read preference

Choose an option to define read preference options when querying data. Available options are:

Primary
Primary preferred
Secondary
Secondary preferred
Nearest

Default value: Primary

Account Encryption

Standard Encryption	If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.
Enhanced Encryption	If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account. Account: High: Password Medium + High: Username, Password Low + Medium + High: Hostname, Database name, Username, Password

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

High: Password
Medium + High: Username, Password
Low + Medium + High: Hostname, Database name, Username, Password

Snap Pack History

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
February 2025	440patches29949	17 Feb 2025	Latest	Upgraded the Spring Framework version to 5.3.39.
February 2025	main29887	12 Feb 2025	Stable	Updated and certified against the current SnapLogic Platform release.
November 2024	main29029	13 Nov 2024	Stable	Enhanced the MongoDB Replica and Mongo ReplicaSet Dynamic Accounts to define read preference options when querying data. The default option is Primary, so you cannot allocate read load to the secondary node. Note that the Secondary preferred mode is not supported for the MongoDB Execute Snap.
August 2024	main27765	21 Aug 2024	Stable	Updated and certified against the current SnapLogic Platform release.
May 2024	437patches27343	30 Jul 2024	Latest	The MongoDB - Atlas Vector Search Snap now supports the following: Suggestions for the Search index field that enables the Snap to populate the associated indices in the list. The input schema displays the mandatory vector field and optional filter suggestion (if the Search index contains a filter type query) in alignment with the fields expected by the Snap.
May 2024	437patches26832	24 Jun 2024	Latest	Fixed the inconsistency in `ObjectId` and `Date` representation in the output preview between MongoDB - Execute and MongoDB - Find snaps. Enhanced the MongoDB Execute Snap with the Timezone Offset field set that enables you to apply the timezone offset on the date fields.
May 2024	437patches26721	12 Jun 2024	Latest	Added Number of retries and Retry interval (seconds) fields, to MongoDB Delete, Update, Find, Group, Insert, and Atlas Vector Search Snaps that enable you to handle retries during a connection failure. Fixed an issue with the MongoDB - Execute Snap, where data was missing when the database server restarted and the error view was enabled. Fixed an issue with the MongoDB - Execute Snap where the log file missed the retry attempts information.
May 2024	main26341	08 May 2024	Stable	Enhanced the MongoDB Update Snap with the Array Filters field, which enables you to use array filters in the update operation. Additionally, the Update Query field is modified into a text box for visibility and usability of input queries. Upgraded Spring dependencies to the latest supported Java 11 version for MongoDB Snap Pack.
February 2024	436patches26244	01 May 2024	Latest	Added the following Snap to the MongoDB Snap Pack: MongoDB - Atlas Vector Search: Performs advanced vector-based queries, such as Similarity searches, Approximate Nearest Neighbor (ANN) queries, and Range queries on vector data stored in MongoDB Atlas.
February 2024	436patches25893	10 Apr 2024	Latest	Added MongoDB Execute Snap to the MongoDB Snap Pack.
February 2024	main25112	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	main23721	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	main22460	16 Aug 2023	Stable	Updated and certified against the current SnapLogic Platform release.
May 2023	main21015	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	main19844	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	main18944	10 Nov 2022	Stable	Upgraded with the latest SnapLogic Platform release.
September 2022	430patches18223	27 Sep 2022	Latest	The MongoDB Update Snap in a low-latency feed Ultra Pipeline now correctly acknowledges the requests.
August 2022	430patches17472	18 Aug 2022	Latest	The MongoDB Account with Encryption type set to TLS/SSL does not fail with the "URL cannot be null" error.
August 2022	main17386	11 Aug 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.29Patches	429patches15807	23 Jun 2022	Latest	Updated the expected output for the MongoDB - Update Snap that is changed because of the upgrade of Spring Core framework version.
4.29	main15993	14 May 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.28	main14627	12 Feb 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.27	main12833	13 Nov 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.26	main11181	14 Aug 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.25	main9554	08 May 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.24	main8556	13 Feb 2021	Stable	Fixed an issue in the MongoDB accounts to connect to Atlas Free Tier and Shared Cluster database using the Use cursor timeout checkbox in the MongoDB cursor properties. If selected, this option enables the server to close a cursor automatically after a period of inactivity. For the existing accounts that does not have this field, the value for this checkbox returns false, which is backward compatible.
4.23	main7430	14 Nov 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.22	main6403	12 Sep 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.21 Patch	421patches6272	27 Jul 2020	Latest	Fixes the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected.
4.21 Patch	421patches6144	20 Jul 2020	Latest	Fixes the following issues with DB Snaps: The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive. Connection leaks occur during Pipeline execution.
4.21 Patch	MULTIPLE8841	19 May 2020	Latest	Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.
4.21	snapsmrc542	09 May 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.20	snapsmrc535	08 Feb 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.19	snaprsmrc528	14 Nov 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.18	snapsmrc523	10 Aug 2019	Stable	Added the following fields to the Mongo DB Find Snap: Projection Condition, Sort Condition, Offset, Limit, and Group result. Added a new Snap, MongoDB Group, which enables you to group input documents by a specified expression, and output to the next stage, one document for each distinct grouping. Added a new field to the Mongo DB Update Snap, Update operation and Exclude list, which enable you to update operations and exclude a list of JSON properties before sending the updated documents to MongoDB.
4.17	ALL7402	11 Jun 2019	Latest	Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17 Patch	db/mongo7331	24 May 2019	Latest	Fixed an issue with the MongoDB - Update Snap wherein the Snap converts all non-updated integer and float data types to string data type. Fixed a Null Pointer Exception for old MongoDB accounts that did not have driver jars.
4.17	snapsmrc515	11 Jun 2019	Latest	Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.
4.16	snapsmrc508	16 Feb 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.15 Patch	db/mongo6783	18 Feb 2019	Latest	Fixed connection timeout issue with MongoDB.
4.15 Patch	db/mongo6465	09 Jan 2019	Latest	Fixed an issue wherein REST calls to Ultra tasks returned an error message.
4.15	snapsmrc500	15 Dec 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.14 Patch	db/mongo5666	13 Aug 2018	Latest	Fixed the Update, Delete, and Find Snaps to populate input view schema for a given table, similar to the Insert Snap.
4.14	snapsmrc490	11 Aug 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.13 Patch	mongo5537	24 Jul 2018	Latest	Fixed the Update, Delete, and Find Snaps to populate input view schema for a given table, similar to the Insert Snap.
4.13	snapsmrc486	12 May 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.12	snapsmrc480	17 Feb 2018	Stable	Added the SSl certification properties to all the MongoDB Accounts to ensure the validation of the certificate.
4.11	snapsmrc465	11 Nov 2017	Stable	Upgraded with the latest SnapLogic Platform release.
4.10 Patch	mongo3978	05 Oct 2017	Latest	Resolved an issue where the NumberFormatException was not handled properly for some of the valid Number Types like "NaN"/ "+Infinity"/ "-Infinity".
4.10	snapsmrc414	12 Aug 2017	Stable	Upgraded with the latest SnapLogic Platform release.
4.9.0 Patch	mongodb3259	17 Jul 2017	Latest	Addressed an issue in MongoDB Update where Upsert Date failed with "Can't find a codec for class org.joda.time". MongoDB Insert Snap - Collectio name expression evaluate fixed.
4.9	snapsmrc405	13 May 2017	Stable	Query Condition property is now an expression that evaluates to an object or JSON string. Updated the Snap with Database name property to support the users defined in an authentication database.
4.8.0 Patch	mongodb2735	14 Mar 2018	Latest	Added SSL encryption type to all MongoDB accounts and Replica set Accounts and removed the MongoDB SSL account.
4.8	snapsmrc398	11 Feb 2017	Stable	The MongoDB Delete Snap and MongoDB Update Snap were introduced in this release. Enhanced the MongoDB Snap account with SSL Account type. Updated the Batch Size property in MongoDB Find with the default value of 0. Enhanced the MongoDB Find Snap documentation with an example. Info tab added to accounts. Database accounts now invalidate connection pools if account properties are modified and login attempts fail.
4.7 Patch	mongo2375	06 Jan 2018	Latest	Update the MongoDB java driver to 3.0.4; Add exception handling to each record processing. MongoDB SSL Account removed and replaced with the new configuration for all the Accounts (Encryption type Property).
4.7 Patch	mongo2338	27 Dec 2017	Latest	Add an account for MongoDB SSL connection without certificates validation
4.7 Patch	mongo2200	28 Nov 2017	Latest	Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter.
4.7	snapsmrc382	23 Nov 2016	Stable	Updated the Snap account with the LDAP Authentication type.
4.6	snapsmrc362	13 Aug 2016	Stable	Resolved an issue in MongoDB Insert Snap that processed and inserted all numeric fields as strings.
4.5.1	snapsmrc344	18 May 2016	Stable	Resolved and issue with MongoDB Insert with an empty input view failed. Resolved an issue with MongoDB Insert that changed a numeric type field in MongoDB as String. Resolved an issue that caused Snap execution failures when accessing MongoDB using a Replica Set account.
4.3.2		15 Jan 2016	Stable	Resolved an issue with MongoDB Find returning nothing when nothing was found.
4.3			Stable	Resolved an issue with an incorrect resolution displaying during account validation if the username was blank. Resolved an issue in the MongoDB Find Snap with nested arrays. Resolved an issue in MongoDB Find with data not being usable be other Snaps.
4.2.2			Stable	Username and Password are no longer required fields when creating a MongoDB account because it is possible to configure an instance where that information is not required. MongoDB Aaccount now supports Mongo Java Driver 3.0.2. MongoDB Find Resolved an issue with MongoDB Find not properly supporting the expression language. Resolved an issue with MongoDB Find returning "Current context not an ARRAY but OBJECT" for a deep nested ObjectId object. Resolved an issue with MongoDB Find when data had built-in datatype. Resolved a null pointer exception in MongoDB Find. Resolved an issue with MongoDB Find not routing failed documents to the error view. Resolved an issue with MongoDB error handling when maximum number of documents reached. Improved the error message presented when MongoDB database could not reach the JCC.
4.2.1			Stable	MongoDB - Find: Resolved Error- Failure: java.util.HashMap cannot be cast to java.lang.String when in query condition passes without single quotes. MongoDB - Find: Resolved failure with Query Using Operators. Resolved MongoDB driver and account do not support current version of MongoDB. Resolved a failure MongoDB Insert with custom _id.

Browser not supported