> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/hashicorp-vault.md).

# HashiCorp Vault

Configure the HashiCorp Vault credential entry in Remote Desktop Manager to inject secrets automatically into RDP, SSH, VNC, and SFTP sessions.

Linking your secrets in HashiCorp Vault to Remote Desktop Manager sessions allows credentials to be injected automatically when launching connections, eliminating the need for manual copying and reducing the risk of exposure. This topic covers the settings for the entry located under ***Add new entry*** – ***Credential management*** – ***HashiCorp Vault***.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr></tbody></table>

<table><thead><tr><th width="242.79998779296875">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>The URL of your HashiCorp Vault instance. This field is required and must contain a valid URL.</td></tr><tr><td><strong>Namespace</strong></td><td>Specifies the namespace within your HashiCorp Vault instance. Use this if your Vault environment is configured with enterprise namespaces to logically separate data or manage multi-tenancy. Leave blank if not applicable.</td></tr><tr><td><strong>Use "My account settings"</strong></td><td>Enable this option to reuse account settings you have <a href="/rdm/ribbon-menu-bar/file/my-account-settings.md">configured</a> under <em><strong>File</strong></em> – <em><strong>My account settings</strong></em>. When enabled, the authentication fields of the entry are unavailable. This option is hidden when a policy disables <em><strong>My account settings</strong></em>.</td></tr><tr><td><strong>Authentication method</strong></td><td><p>Select the authentication method to align with your environment’s identity policies:</p><ul><li><strong>Token</strong></li><li><strong>LDAP</strong></li><li><strong>Radius</strong></li><li><strong>UserPass</strong></li></ul></td></tr><tr><td><strong>Token</strong></td><td>The token used to authenticate to HashiCorp Vault. Displayed when <em><strong>Authentication method</strong></em> is set to <em><strong>Token</strong></em>, and required unless <em><strong>Use "My account settings"</strong></em> is enabled.</td></tr><tr><td><strong>Username</strong></td><td>The username used to authenticate to HashiCorp Vault. Displayed when <em><strong>Authentication method</strong></em> is set to <em><strong>LDAP</strong></em>, <em><strong>Radius</strong></em>, or <em><strong>UserPass</strong></em>, and required unless <em><strong>Use "My account settings"</strong></em> is enabled.</td></tr><tr><td><strong>Password</strong></td><td>The password used to authenticate to HashiCorp Vault. Displayed when <em><strong>Authentication method</strong></em> is set to <em><strong>LDAP</strong></em>, <em><strong>Radius</strong></em>, or <em><strong>UserPass</strong></em>. Unavailable when <em><strong>Always ask for password</strong></em> is enabled, and disabled when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</td></tr><tr><td><strong>Always ask for password</strong></td><td>Prompt for the HashiCorp Vault password every time it is needed. Displayed when <em><strong>Authentication method</strong></em> is set to <em><strong>LDAP</strong></em>, <em><strong>Radius</strong></em>, or <em><strong>UserPass</strong></em>.</td></tr><tr><td><strong>Mount path</strong></td><td>The mount path of the authentication method in HashiCorp Vault. Leave blank to use the default path of the method. Displayed when <em><strong>Authentication method</strong></em> is set to <em><strong>LDAP</strong></em>, <em><strong>Radius</strong></em>, or <em><strong>UserPass</strong></em>.</td></tr><tr><td><strong>Secret</strong></td><td>The path of the secret that holds the credentials. Click the browse button to select a secret from your HashiCorp Vault instance. This field is required unless <em><strong>Always prompt with list</strong></em> is enabled, in which case it is unavailable.</td></tr><tr><td><strong>Always prompt with list</strong></td><td>When enabled, this will force Remote Desktop Manager to prompt the user to select a secret each time a connection is launched. Useful if different credentials are used frequently.</td></tr></tbody></table>

### Injecting HashiCorp Vault credentials in a session

Learn how to retrieve and inject stored credentials from HashiCorp Vault directly into your sessions. Supported session types include RDP, SSH, VNC, SFTP, and more.

In this example, we will create an RDP session. Go to ***Add new entry*** – ***Session*** – ***RDP (Microsoft Remote Desktop)***. In the ***Credentials*** field, select ***Linked (vault)*** and choose the HashiCorp Vault entry you previously created that contains your credentials. Once you have filled in the required RDP settings, click ***Add*** or ***Save and open*** to launch the session.

Select the secret in the ***HashiCorp Vault secrets list*** to open the RDP session.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/hashicorp-vault.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.