> 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/jwt-json-web-token.md).

# JWT (JSON Web Token)

Configure the JWT (JSON Web Token) entry in Remote Desktop Manager to generate and store JSON web tokens and related login credentials.

The ***JWT (JSON Web Token)*** entry allows users to securely generate and store JSON web tokens, as well as related metadata and credentials, in Remote Desktop Manager.

<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>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Entry type</strong></td><td><p>Choose a method to retrieve the JSON Web Token between:</p><ul><li><strong>File (local)</strong>: Retrieve a token from a file located on the local computer.</li><li><strong>Embedded data</strong>: Use a generated token from the <em><strong>JWT generator</strong></em> integrated into Remote Desktop Manager.</li></ul></td></tr><tr><td><strong>Generate a new package with the current selection</strong></td><td>Available when <em><strong>Entry type</strong></em> is set to <em><strong>Embedded data</strong></em>. This button next to <em><strong>Entry type</strong></em> opens the JWT generator window, in which you can determine which <em><strong>Algorithm</strong></em> to use, enter <em><strong>Claims</strong></em> and <em><strong>Custom claims</strong></em>, and preview what the token package will look like. The generated token is placed in the <em><strong>JWT token</strong></em> field.</td></tr><tr><td><strong>Secret key</strong></td><td>Decryption key of the token. This field is automatically filled when generating a new token. The field can be made visible by clicking the <em><strong>Show password</strong></em> button next to it.</td></tr><tr><td><strong>File</strong></td><td>Available when <em><strong>Entry type</strong></em> is set to <em><strong>File (local)</strong></em>. Select the JWT file to read the token from. This field is required, and the file must exist when the entry is saved. Variables are allowed in the path.</td></tr><tr><td><strong>JWT token</strong></td><td><p>The token retrieved from the file or stored in the entry, displayed as read-only text. The buttons around this field are:</p><ul><li><strong>Export</strong> — Save the token to a file.</li><li><strong>View</strong> — Open the token in the JWT generator window without generating a new token.</li><li><strong>Paste from clipboard</strong> — Use the token currently in the clipboard. Available in <em><strong>Embedded data</strong></em> mode.</li><li><strong>Clear</strong> — Remove the stored token. Available in <em><strong>Embedded data</strong></em> mode.</li><li><strong>Load from file</strong> — Load the token from a file and store it in the entry. Available in <em><strong>Embedded data</strong></em> mode.</li><li><strong>Copy</strong> — Copy the token to the clipboard.</li></ul><p>A token is required in <em><strong>Embedded data</strong></em> mode. <em><strong>Export</strong></em>, <em><strong>View</strong></em> and <em><strong>Copy</strong></em> are shown only when a token is present.</p></td></tr></tbody></table>

### Login name

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Username</strong></td><td>This username will be used when authenticating into sessions using the JWT entry as linked credentials.</td></tr><tr><td><strong>Password</strong></td><td>Enter the password associated with the username. Generate a password or use the <a href="/rdm/ribbon-menu-bar/tools/password-generator.md">Password generator</a>. The password can be revealed or hidden by clicking the eye icon.</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/jwt-json-web-token.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.
