MongoDB database plugin HTTP API
Note: This engine can use external X.509 certificates as part of TLS or signature validation. Verifying signatures against X.509 certificates that use SHA-1 is deprecated and is no longer usable without a workaround starting in Vault 1.12. See the deprecation FAQ for more information.
The MongoDB database plugin is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the MongoDB database.
Configure connection
In addition to the parameters defined by the Database Backend, this plugin has a number of parameters to further configure a connection.
Method | Path |
---|---|
POST | /database/config/:name |
Parameters
connection_url
(string: <required>)
– Specifies the MongoDB standard connection string (URI). This field can be templated and supports passing the username and password parameters in the following format {{field_name}}. A templated connection URL is required when using root credential rotation.write_concern
(string: "")
- Specifies the MongoDB write concern. This is set for the entirety of the session, maintained for the lifecycle of the plugin process. Must be a serialized JSON object, or a base64-encoded serialized JSON object. The JSON payload values map to the values in the Safe struct from the mgo driver.username
(string: "")
- The root credential username used in the connection URL.password
(string: "")
- The root credential password used in the connection URL.tls_certificate_key
(string: "")
- x509 certificate for connecting to the database. This must be a PEM encoded version of the private key and the certificate combined.tls_ca
(string: "")
- x509 CA file for validating the certificate presented by the MongoDB server. Must be PEM encoded.username_template
(string)
- Template describing how dynamic usernames are generated.
Default Username Template
Example Usernames:
Example | |
---|---|
DisplayName | token |
RoleName | myrolename |
Username | v-token-myrolename-jNFRlKsZZMxJEx60o66i-1614294836 |
Example | |
---|---|
DisplayName | amuchlonger_dispname |
RoleName | role-name-with-dashes |
Username | v-amuchlonger_dis-role-name-with--jNFRlKsZZMxJEx60o66i-1614294836 |
Sample payload
Sample request
Statements
Statements are configured during role creation and are used by the plugin to determine what is sent to the database on user creation, renewing, and revocation. For more information on configuring roles see the Role API in the database secrets engine docs.
Parameters
The following are the statements used by this plugin. If not mentioned in this list the plugin does not support that statement type.
creation_statements
(string: <required>)
– Specifies the database statements executed to create and configure a user. Must be a serialized JSON object, or a base64-encoded serialized JSON object. The object can optionally contain adb
string for session connection, and must contain aroles
array. This array contains objects that holds arole
, and an optionaldb
value, and is similar to the BSON document that is accepted by MongoDB'sroles
field. Vault will transform this array into such format. For more information regarding theroles
field, refer to MongoDB's documentation.revocation_statements
(string: "")
– Specifies the database statements to be executed to revoke a user. Must be a serialized JSON object, or a base64-encoded serialized JSON object. The object can optionally contain adb
string. If nodb
value is provided, it defaults to theadmin
database.
Sample creation statement
Sample revocation statement