backport of commit 5ab5369ba2ea7a861536687b4aa447ae3a2cb31c (#22399)

Co-authored-by: Kai Xia(夏恺) <xiaket@users.noreply.github.com>
This commit is contained in:
hc-github-team-secure-vault-core 2023-08-17 09:42:34 -04:00 committed by GitHub
parent 9d87817431
commit d21e8cdfed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 0 deletions

View File

@ -17,6 +17,11 @@ it uses a public and private key pair to authenticate.
See the [database secrets engine](/vault/docs/secrets/databases) docs for
more information about setting up the database secrets engine.
<Note>
The information below relates to the MongoDB Altas <b>database plugin</b> for the Vault database secrets engine.
Refer to the <a href="vault/docs/secrets/mongodbatlas">MongoDB Atlas secrets engine</a>
for information about using the MongoDB Atlas secrets engine for the Vault.
</Note>
## Capabilities
| Plugin Name | Root Credential Rotation | Dynamic Roles | Static Roles | Username Customization | Credential Types |

View File

@ -16,6 +16,13 @@ project or organization with appropriate role(s). The MongoDB Atlas Programmatic
Private Keys are returned to the caller. To learn more about Programmatic API Keys visit the
[Programmatic API Keys Doc](https://docs.atlas.mongodb.com/reference/api-docs/apiKeys/).
<Note>
The information below relates to the MongoDB Altas <b>secrets engine</b>. Refer to the
<a href="vault/docs/secrets/databases/mongodbatlas">MongoDB Atlas database secrets engine</a>
for information about using the MongoDB Atlas database plugin for the Vault
database secrets engine.
</Note>
## Setup
Most Secrets Engines must be configured in advance before they can perform their functions. These