Connecting to MongoDB

Principle

The connect dialog can be used to create a MongoClient instance connected to a MongoDB single instance, replica set, or sharded cluster. Several MongoClient instances can be connected and managed by UMongo.

Options

The following options are supported:

Advanced options

The following options are supported:

Connecting with SSL

To connect using SSL, use the 'SSL' socketType in the Connect Dialog.
If using self-signed certificates (for either client or server), use the 'SSL no validation' socketType.

UMongo relies on Java's SSL utilities, for more information please refer to Java and Keytool documentation.
Paths to the keyStore and trustStore can be entered under the Security tab in the Preferences Dialog.
UMongo will prompt for a password, but it will not store it on disk.

Setting up the client SSL certificate

The client certificate can be added through the Java Keystore. Assuming you have a ".pem" certificate file, convert it to pkcs12 using:
    openssl pkcs12 -export -in client-cert.pem -out client-cert.p12
    
From the p12 file you can create the keystore:
    keytool -importkeystore -srckeystore client-cert.p12 -srcstoretype PKCS12 -destkeystore keystore.jks
    

Adding a Certificate Authority file

Adding a CA file is done using keytool
    keytool -import -trustcacerts -alias root -file Thawte.crt -keystore keystore.jks
    

Proxy options

The following options are supported: If MongoDB is not accessible from your local machine, but you can SSH to a server that can connect, do the following:

Examples

Following are possible connections: