> 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/configure-certificate-x.509-credential-entry-type.md).

# Configure certificate x.509 credential entry type

Configure a Certificate X.509 credential entry in Remote Desktop Manager to store certificates for RDP smart card authentication.

The ***Certificate (X.509)*** credential entry type facilitates RDP Smart Card authentication, and stores the full X.509 certificate (public and private portion) for insertion into an RDP virtual Smart card.

Some organizations use X.509 certificates as as alternative to authenticating with user IDs and passwords. X.509 certificates leverage public-private key cryptography, and are widely seen as an enhanced safeguard against malicious network impersonators.

{% hint style="success" %}
For those using the deprecated ***Certificate (.pfx, .cert, .cer, .p12, .pem)*** entry, you may wish to import your certificate in a ***Certificate (X.509)*** entry instead.To do so, head to the deprecated entry, click ***Save document as***, save the certificate as a `.pfx` file. Then, import it as per the [steps below](#stored-in-database).
{% endhint %}

1. Add a new entry in Remote Desktop Manager.
2. Go to ***Credential management***, select ***Certificate (X.509)***, and click ***OK***.
3. Enter a ***Name*** and select a ***Folder***.
4. Under ***General***, select ***Stored in database*** or ***Link to certificate store*** in the ***Certificate data mode*** drop-down menu.

### Stored in database

1. Select ***Update certificate*** under ***General*** – ***Embedded X.509 certificate*** to import an X.509 certificate.
2. Choose the ***Certificate file*** and click ***Next***.
3. Choose a ***Private key file*** if needed and click ***Next***.
4. Click ***Finish*** to close the window.
5. Select ***View certificate*** to view certificate information and install the certificate.
6. In the ***Certificate window***, click ***Install certificate***.
7. Select the ***Store Location***: ***Current user*** or ***Local machine***. Click ***Next***.
8. Choose the ***Certificate store***. Click ***Next***.
9. Click ***Finish*** to complete the import.
10. Select the ***PIN*** of the ***Smart card*** if needed. Click ***Add*** to save the entry.

### Link to certificate store

1. Select ***Current user*** or ***Local machine*** under ***Certificate location***.
2. Choose the ***Certificate store*** in the drop-down menu.
3. Choose ***Thumbprint*** or ***Subject name*** in ***Certificate find type***.
4. Enter the ***Search text***. Click ***Test configuration***.
5. Select the ***PIN*** of the ***Smart card*** if needed. Click ***Add*** to save the entry.


---

# 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/configure-certificate-x.509-credential-entry-type.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.