a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
105 lines
4 KiB
Markdown
105 lines
4 KiB
Markdown
---
|
||
layout: "api"
|
||
page_title: "MongoDB - Database - Secrets Engines - HTTP API"
|
||
sidebar_title: "MongoDB"
|
||
sidebar_current: "api-http-secret-databases-mongodb"
|
||
description: |-
|
||
The MongoDB plugin for Vault's database secrets engine generates database credentials to access MongoDB servers.
|
||
---
|
||
|
||
# MongoDB Database Plugin HTTP API
|
||
|
||
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](/api/secret/databases/index.html#configure-connection), this plugin
|
||
has a number of parameters to further configure a connection.
|
||
|
||
| Method | Path | Produces |
|
||
| :------- | :--------------------------- | :--------------------- |
|
||
| `POST` | `/database/config/:name` | `204 (empty body)` |
|
||
|
||
### 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][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][mgo-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.
|
||
|
||
### Sample Payload
|
||
|
||
```json
|
||
{
|
||
"plugin_name": "mongodb-database-plugin",
|
||
"allowed_roles": "readonly",
|
||
"connection_url": "mongodb://{{username}}:{{password}}@mongodb.acme.com:27017/admin?ssl=true",
|
||
"write_concern": "{ \"wmode\": \"majority\", \"wtimeout\": 5000 }",
|
||
"username": "admin",
|
||
"password": "Password!"
|
||
}
|
||
```
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
--request POST \
|
||
--data @payload.json \
|
||
http://127.0.0.1:8200/v1/database/config/mongodb
|
||
```
|
||
|
||
## 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](/api/secret/databases/index.html#create-role) 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 a "db" string for session connection,
|
||
and must contain a "roles" array. This array contains objects that holds
|
||
a "role", and an optional "db" value, and is similar to the BSON document that
|
||
is accepted by MongoDB's `roles` field. Vault will transform this array into
|
||
such format. For more information regarding the `roles` field, refer to
|
||
[MongoDB's documentation](https://docs.mongodb.com/manual/reference/method/db.createUser/).
|
||
|
||
- `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 a "db" string. If no
|
||
"db" value is provided, it defaults to the "admin" database.
|
||
|
||
### Sample Creation Statement
|
||
|
||
```json
|
||
{
|
||
"db": "admin",
|
||
"roles": [
|
||
{
|
||
"role": "read",
|
||
"db": "foo"
|
||
}
|
||
]
|
||
}
|
||
```
|
||
[mongodb-write-concern]: https://docs.mongodb.com/manual/reference/write-concern/
|
||
[mgo-safe]: https://godoc.org/gopkg.in/mgo.v2#Safe
|