> 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/troubleshooting-articles/saml-troubleshooting-for-cyberark-dashboard.md).

# SAML troubleshooting for CyberArk dashboard

Fix an empty safe selector in the CyberArk Dashboard SAML authentication entry by updating Remote Desktop Manager and clearing the WebView2 cache.

When connecting to your ***CyberArk Dashboard*** entry configured with SAML authentication, you may encounter an issue where your safe selector is empty. We recommend updating Remote Desktop Manager to at least version 2023.2.18 as improvements have been implemented in this version for the SAML authentication mode.

1\. [Download and install](https://devolutions.net/remote-desktop-manager) Remote Desktop Manager or update it to version 2023.2.18 or later.

{% hint style="success" %}
If you are using a Team workspace, we recommend to use a [portable version of Remote Desktop Manager](/rdm/getting-started/installation/client/portable-usb.md) on a local workspace to test.
{% endhint %}

2. In Remote Desktop Manager, create your ***CyberArk Dashboard*** entry. Make sure to created it from version 2023.2.18 or later and **not** from the previous version.
3. Enter the necessary information. See [CyberArk Dashboard Configuration and Use](/rdm/knowledge-base/how-to-articles/cyberark-dashboard-configuration-and-use.md) for more information.
4. Once your entry is created, go to ***File – Settings – Advanced***.
5. Click the link at the bottom that leads to your Remote Desktop Manager configuration files.
6. Open the folder called "WebView2.Cache", then delete the "CyberArk\_SAML" folder that is inside.
7. Try to connect again to your entry. You may need to refresh or restart Remote Desktop Manager for this solution to work.


---

# 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/troubleshooting-articles/saml-troubleshooting-for-cyberark-dashboard.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.