> 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/common-settings/one-time-password.md).

# One-time password

Configure the one-time password of an entry in Remote Desktop Manager, its source and how the code is combined with the credentials.

The ***One-time password*** section defines the one-time password (OTP) that an entry uses: where the OTP comes from and how its code is combined with the credentials when the session opens. To store an OTP key as an entry of its own, use the [One-time password](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/one-time-password.md) entry type instead.

Available for session entries, folders, the vault, and information entries of the ***Website (legacy)*** type. In the entry properties, select ***Connection*** – ***One-time password***. For the vault, go to ***Administration*** – ***Vault settings***.

With [batch edit](https://docs.devolutions.net/rdm/ribbon-menu-bar/edit/batch-edit.md), select ***Override OTP*** to replace these settings on every selected entry. For examples of use, see [One-time password (OTP) usage with entries](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/one-time-password-otp-usage-with-entries.md).

### General

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Source</strong></em></td><td><p>Where the OTP comes from:</p><ul><li><em><strong>Configured</strong></em>: an OTP key configured in the entry, in the <em><strong>One-time password</strong></em> group.</li><li><em><strong>Linked</strong></em>: a credential entry of a vault. Select the vault in the <em><strong>Vault</strong></em> list, then select the credential entry. Other vaults are listed when the workspace supports links to other vaults. Selecting the user vault from an entry in a shared vault finds, for each user, the credential entry of their user vault whose name matches the name you enter.</li><li><em><strong>Inherited</strong></em>: the OTP of the parent folder. The value that applies is shown under the list. Not offered for the vault.</li><li><em><strong>No entry configuration</strong></em>: no OTP is configured in the entry. This is the default value. The information icon explains that OTPs not in the current vault, including third-party credentials, are not resolved.</li><li><em><strong>Prompt</strong></em>: opens a window where the user types the OTP code when the session opens.</li><li><em><strong>Current session credentials</strong></em>: the OTP of the credentials of the entry.</li></ul><p>With <em><strong>Linked</strong></em>, a link under the credential field selects the value to use when the credential entry holds several values.</p></td></tr></tbody></table>

### One-time password

Shown with the ***Configured*** source.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Key</strong></em></td><td>The secret key that generates the codes, in Base32 or Base64 format. The <em><strong>Load from image</strong></em> button reads the key and its settings from a QR code image. The key can be revealed in private entries, or with the permission to view QR codes in the vault.</td></tr><tr><td><em><strong>Account</strong></em></td><td>The account the OTP belongs to. A warning icon is shown if the name contains the <code>:</code> character, which is replaced by <code>_</code> in the generated QR code.</td></tr><tr><td><em><strong>Application</strong></em></td><td>The service or application the OTP is for. The same warning about the <code>:</code> character applies.</td></tr><tr><td><em><strong>Recovery codes</strong></em></td><td>Opens a window to store the recovery codes of the account.</td></tr></tbody></table>

### Advanced

Shown with the ***Configured*** source.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Time step</strong></em></td><td>Validity period of a code, in seconds (15 or more). The default value is 30.</td></tr><tr><td><em><strong>Code size</strong></em></td><td>Number of digits of the code: <em><strong>6 digits</strong></em> or <em><strong>8 digits</strong></em>. The default value is <em><strong>6 digits</strong></em>.</td></tr><tr><td><em><strong>Hash algorithm</strong></em></td><td>Algorithm used to generate the codes: <em><strong>SHA-1</strong></em>, <em><strong>SHA256</strong></em> or <em><strong>SHA-512</strong></em>. The default value is <em><strong>SHA-1</strong></em>.</td></tr></tbody></table>

### Usage

Not shown with the ***No entry configuration*** source.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Mode</strong></em></td><td><p>How the OTP code is used when the session opens:</p><ul><li><em><strong>None</strong></em>: the code is not added to the credentials. This is the default value.</li><li><em><strong>Append to the password</strong></em> or <em><strong>Prepend to the password</strong></em>: adds the code after or before the password.</li><li><em><strong>Append to the username</strong></em> or <em><strong>Prepend to the username</strong></em>: adds the code after or before the username.</li><li><em><strong>Specific to session</strong></em>: the session type uses the code its own way, when it supports OTPs. The information icon next to the list describes this mode.</li><li><em><strong>Inherited</strong></em>: the usage of the parent folder, shown under the list. Not offered for the vault.</li><li><em><strong>Append and use push notifications</strong></em>: adds the push string after the password, without a code, for services that send a push notification to approve the sign-in.</li></ul></td></tr><tr><td><em><strong>Combination string</strong></em></td><td>Text placed between the credential and the code, such as a separator. Shown with the append and prepend modes. With <em><strong>Append and use push notifications</strong></em>, the field is named <em><strong>Push string</strong></em>; when it is empty, <code>,push</code> is used.</td></tr></tbody></table>


---

# 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/common-settings/one-time-password.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.
