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

# Certificate security provider in a published app environment

Grant certificate read permissions in a published app environment like Citrix so Remote Desktop Manager can use a Certificate Security Provider.

When configuring a Certificate Security Provider in a published app environment (Citrix, RemoteApp, XenApp) as a Security Provider, the user who will run Remote Desktop Manager in the RemoteApp environment (Citrix) will require a Read permission on the certificate. If the Read permission is not correctly set, Remote Desktop Manager will generate the CryptographicException - Keyset does not exist error dialog.

These steps require that the certificate has been successfully installed on the machine on which Remote Desktop Manager will run.

1. Open ***Local Machine Certificate Manager*** on the machine (certlm.msc).
2. Locate the ***Certificates***.
3. Right click on ***Certificates - All Tasks - Manage Private Keys***.
4. Grant the ***Read permission*** over the certificate file to the proper group(s) or user(s).

{% hint style="info" %}
Follow Window's [Service failure with CryptographicException - Keyset does not exist](https://learn.microsoft.com/en-us/archive/blogs/dsnotes/service-failure-with-cryptographicexception-keyset-does-not-exist) blog article to discover more methods of finding the certificate file.
{% 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/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.