> 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/da/knowledge-base/knowledge-base-articles/entry-settings/cyberark-sia.md).

# CyberArk SIA

Konfigurer poster af typen CyberArk SIA i Remote Desktop Manager, herunder SIA-underdomænet, MFA-cachelagring og det valgfrie brugernavn og den valgfrie adgangskode til SSH.

Denne artikel beskriver de mange indstillinger og valgmuligheder, der er tilgængelige for poster af typen ***CyberArk SIA*** i Remote Desktop Manager.

{% hint style="info" %}
En gyldig CyberArk-licens er påkrævet. Uden den er indstillingerne utilgængelige, og meddelelsen "Licensnøgle er påkrævet" vises. For at knytte denne post til en session, se [CyberArk SIA-post](/rdm/da/knowledge-base/how-to-articles/cyberark-sia-entry.md).
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>INDSTILLINGER</strong></td><td><strong>BESKRIVELSE</strong></td></tr><tr><td><strong>Navn</strong></td><td>Navnet på posten.</td></tr><tr><td><strong>Mappe</strong></td><td>Den mappe, hvor posten findes.</td></tr><tr><td><strong>Visning</strong></td><td>Hvordan posten vises. Denne posttype understøtter kun den eksterne visningstilstand, så valget er låst.</td></tr><tr><td><strong>Legitimationsoplysninger</strong></td><td>Kilden til legitimationsoplysningerne. Når legitimationsoplysningerne kommer fra en anden kilde, er felterne <em><strong>Brugernavn</strong></em> og <em><strong>Adgangskode</strong></em> på fanen <em><strong>Generelt</strong></em> utilgængelige.</td></tr></tbody></table>

### Generelt

<table><thead><tr><th width="220">INDSTILLINGER</th><th>BESKRIVELSE</th></tr></thead><tbody><tr><td><strong>Underdomæne</strong></td><td>Underdomænet for Deres CyberArk SIA-instans. Obligatorisk.</td></tr><tr><td colspan="2"><strong>Valgfri (kun SSH)</strong></td></tr><tr><td><strong>Brug MFA-cachelagring</strong></td><td>Brug MFA-cachelagring i CyberArk i stedet for et brugernavn og en adgangskode. Når indstillingen er valgt, er felterne <em><strong>Brugernavn</strong></em> og <em><strong>Adgangskode</strong></em> utilgængelige, og de gemmes ikke.</td></tr><tr><td><strong>Brugernavn</strong></td><td>Det brugernavn, der bruges til SSH-sessioner. Det ignoreres, når noget andet startes.</td></tr><tr><td><strong>Adgangskode</strong></td><td>Den adgangskode, der bruges til SSH-sessioner. Den ignoreres, når noget andet startes.</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/da/knowledge-base/knowledge-base-articles/entry-settings/cyberark-sia.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.