> 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/how-to-articles/keeper-credential-entry-settings.md).

# Indstillinger for Keeper-legitimationspost

Konfigurer legitimationsposten for Keeper i Remote Desktop Manager for at hente boksens legitimationsoplysninger via metoderne Bokslogon eller Enterprise SSO.

Keeper er en af flere eksterne adgangskodeadministratorer, der er integreret i Remote Desktop Manager

{% hint style="info" %}
Integrationen af legitimationsoplysninger fra adgangskodeadministratorer er kun tilgængelig i Team-versionen af Remote Desktop Manager.
{% endhint %}

### Indstillinger

***Logontype*** bestemmer den metode, Remote Desktop Manager bruger til at oprette forbindelse til Keeper.

* ***Bokslogon*** bruger e-mailadressen ***E-mail*** og en ***Hovedadgangskode*** til at logge på.
* ***Enterprise SSO*** bruger e-mailadressen ***E-mail*** til at logge på.
* ***Enterprise SSO (domæne)*** bruger ***Virksomhedsdomæne*** til at logge på.

Valgmuligheden ***Brug “Indstillinger for min konto”***, som er tilgængelig for logontyperne ***Bokslogon*** og ***Enterprise SSO***, lader posten henvise til de legitimationsoplysninger, der er gemt under ***Fil - Indstillinger for min konto***, i stedet for at angive dem manuelt i Keeper-posten.

***Område*** giver Dem mulighed for at vælge, hvor Deres Keeper-server er placeret.

Valgmuligheden ***Spørg altid om adgangskode*** beder Dem om at angive Deres Keeper-adgangskode, hver gang posten bruges, i stedet for at gemme den i posten.

Feltet ***Legitimationsoplysninger*** bruges til at angive, hvilken legitimationsoplysning der hentes fra Keeper.

Valgmuligheden ***Spørg altid med en liste*** giver brugerne mulighed for at vælge legitimationsoplysningen, hver gang posten bruges, i stedet for at fastlægge den.

### Fremgangsmåde

1. Vælg den ønskede ***Logontype*** (***Bokslogon***, ***Enterprise SSO*** eller ***Enterprise SSO (domæne)***).
2. Angiv de påkrævede oplysninger ud fra den valgte ***Logontype***.
3. Brug feltet ***Legitimationsoplysninger*** til at angive, hvilken legitimationsoplysning der skal hentes fra Keeper, eller brug valgmuligheden ***Spørg altid med en liste*** til at vælge, hvilken legitimationsoplysning der skal hentes, hver gang Keeper-posten bruges.
4. Klik på ***OK***.


---

# 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/how-to-articles/keeper-credential-entry-settings.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.