> 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/certificate-security-provider-in-a-published-app-environment.md).

# Certifikatsikkerhedsudbyder i et miljø med publicerede programmer

Tildel læsetilladelser til certifikatet i et miljø med et publiceret program som Citrix, så Remote Desktop Manager kan bruge en certifikatsikkerhedsudbyder.

Når De konfigurerer en certifikatsikkerhedsudbyder i et miljø med et publiceret program (Citrix, RemoteApp, XenApp) som sikkerhedsudbyder, skal den bruger, der skal køre Remote Desktop Manager i RemoteApp-miljøet (Citrix), have læsetilladelse til certifikatet. Hvis læsetilladelsen ikke er angivet korrekt, viser Remote Desktop Manager dialogboksen med fejlen CryptographicException - Keyset does not exist.

Disse trin kræver, at certifikatet er installeret korrekt på den maskine, hvor Remote Desktop Manager skal køre.

1. Åbn ***Certifikatstyring for lokal computer*** på maskinen (certlm.msc).
2. Find ***Certifikater***.
3. Højreklik på ***Certifikater - Alle opgaver - Administrer private nøgler***.
4. Tildel ***læsetilladelse*** til certifikatfilen til de relevante grupper eller brugere.

{% hint style="info" %}
Følg Windows-blogartiklen [Tjenestefejl med CryptographicException - Keyset does not exist](https://learn.microsoft.com/en-us/archive/blogs/dsnotes/service-failure-with-cryptographicexception-keyset-does-not-exist) for at finde flere metoder til at finde certifikatfilen.
{% endhint %}


---

# 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/certificate-security-provider-in-a-published-app-environment.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.