* 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
5.2 KiB
layout | page_title | sidebar_title | sidebar_current | description |
---|---|---|---|---|
api | RabbitMQ - Secrets Engines - HTTP API | RabbitMQ | api-http-secret-rabbitmq | This is the API documentation for the Vault RabbitMQ secrets engine. |
RabbitMQ Secrets Engine (API)
This is the API documentation for the Vault RabbitMQ secrets engine. For general information about the usage and operation of the RabbitMQ secrets engine, please see the RabbitMQ documentation.
This documentation assumes the RabbitMQ secrets engine is enabled at the
/rabbitmq
path in Vault. Since it is possible to enable secrets engines at any
location, please update your API calls accordingly.
Configure Connection
This endpoint configures the connection string used to communicate with RabbitMQ.
Method | Path | Produces |
---|---|---|
POST |
/rabbitmq/config/connection |
204 (empty body) |
Parameters
-
connection_uri
(string: <required>)
– Specifies the RabbitMQ connection URI. -
username
(string: <required>)
– Specifies the RabbitMQ management administrator username. -
password
(string: <required>)
– Specifies the RabbitMQ management administrator password. -
verify_connection
(bool: true)
– Specifies whether to verify connection URI, username, and password.
Sample Payload
{
"connection_uri": "https://...",
"username": "user",
"password": "password"
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
http://127.0.0.1:8200/v1/rabbitmq/config/connection
Configure Lease
This endpoint configures the lease settings for generated credentials.
Method | Path | Produces |
---|---|---|
POST |
/rabbitmq/config/lease |
204 (empty body) |
Parameters
-
ttl
(int: 0)
– Specifies the lease ttl provided in seconds. -
max_ttl
(int: 0)
– Specifies the maximum ttl provided in seconds.
Sample Payload
{
"ttl": 1800,
"max_ttl": 3600
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
http://127.0.0.1:8200/v1/rabbitmq/config/lease
Create Role
This endpoint creates or updates the role definition.
Method | Path | Produces |
---|---|---|
POST |
/rabbitmq/roles/:name |
204 (empty body) |
Parameters
-
name
(string: <required>)
– Specifies the name of the role to create. This is specified as part of the URL. -
tags
(string: "")
– Specifies a comma-separated RabbitMQ management tags. -
vhost
(string: "")
– Specifies a map of virtual hosts to permissions.
Sample Payload
{
"tags": "tag1,tag2",
"vhost": "{\"/\": {\"configure\":\".*\", \"write\":\".*\", \"read\": \".*\"}}"
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
http://127.0.0.1:8200/v1/rabbitmq/roles/my-role
Read Role
This endpoint queries the role definition.
Method | Path | Produces |
---|---|---|
GET |
/rabbitmq/roles/:name |
200 application/json |
Parameters
name
(string: <required>)
– Specifies the name of the role to read. This is specified as part of the URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/rabbitmq/roles/my-role
Sample Response
{
"data": {
"tags": "",
"vhost": "{\"/\": {\"configure\":\".*\", \"write\":\".*\", \"read\": \".*\"}}"
}
}
Delete Role
This endpoint deletes the role definition.
Method | Path | Produces |
---|---|---|
DELETE |
/rabbitmq/roles/:name |
204 (empty body) |
Parameters
name
(string: <required>)
– Specifies the name of the role to delete. This is specified as part of the URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request DELETE \
http://127.0.0.1:8200/v1/rabbitmq/roles/my-role
Generate Credentials
This endpoint generates a new set of dynamic credentials based on the named role.
Method | Path | Produces |
---|---|---|
GET |
/rabbitmq/creds/:name |
200 application/json |
Parameters
name
(string: <required>)
– Specifies the name of the role to create credentials against. This is specified as part of the URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/rabbitmq/creds/my-role
Sample Response
{
"data": {
"username": "root-4b95bf47-281d-dcb5-8a60-9594f8056092",
"password": "e1b6c159-ca63-4c6a-3886-6639eae06c30"
}
}