MongoDB
A MongoDB connection is a native type, allowing for the auditing of queries and redaction of their output. It facilitates a local TCP connection without requiring a password.
Prerequisites
To get the most out of this guide, you will need to:
- Either create an account in our managed instance or deploy your own hoop.dev instance
- You must be your account administrator to perform the following commands
This integration only accepts SCRAM authentication for native connections.
Features
The table below outlines the features available for this type of connection.
- Native - This refers to when a database client connects through a specific protocol, such as an IDE or client libraries through
hoop connect <connection-name>
. - One Off - This term refers to accessing this connection from hoop web panel.
Feature | Native | One Off | Description |
---|---|---|---|
TLS Termination Proxy | The local proxy terminates the connection with TLS, enabling the connection with the remote server to be TLS encrypted. | ||
Audit | The gateway stores and audits the queries being issued by the client | ||
Data Masking (Google DLP) | A policy can be enabled to mask sensitive fields dynamically when performing queries in the database. | ||
Data Masking (MS Presidio DLP) | A policy can be enabled to mask sensitive fields dynamically when performing queries in the database. | ||
Credentials Offload | The user authenticates via SSO instead of using database credentials. | ||
Interactive Access | Interactive access is available when using an IDE or connecting via a terminal for analysis exploration. |
Configuration
Name | Type | Required | Description |
---|---|---|---|
CONNECTION_STRING | env-var | yes | The MongoDB connection string. See https://www.mongodb.com/docs/manual/reference/connection-string/ for more details about the proper format. |
Connection setup
Create a new Database connection in hoop’s web panel.
Access the connection
You can access it through hoop CLI or hoop web panel.
hoop CLI
Clients must use noop
as both the username and password, along with the directionConnection=true
option
Web panel
Known Issues
Clients advertising the wrong server
The native implementation has a known issue in cluster setups where clients may incorrectly advertise connections to the wrong server. Hoop selects a server at random and attempts to upgrade the connection to the primary server. However, this transition is not properly propagated to clients, resulting in the advertisement of incorrect server information.
Users can manually switch to the primary server after connecting to a secondary server. For example, using mongoshell
: