> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-mp-guide/v19-en-us/infrastructure/certificates/generate-a-self-signed-certificate.md).

# Generate a self-signed certificate

To generate a self-signed certificate, navigate to **Infrastructure** > **Certificates**. Choose **Add** > **Generate self-signed certificate** from the ellipsis menu and specify the following options:

* **Name:** Type a name for this certificate. This field is mandatory.
* **Description**: An optional description.
* **Usage**: Specify whether the certificate should be used for RAS Secure Gateways or HALB, or both. This selection is mandatory.
* **Key size:** The certificate key size, in bits. Here you can select from the predefine values. The default is 2048 bit, which is the minimum required length according to current industry standards.
* **Expire in**: The certificate expiration date.
* **Country code**: Select your country.
* **Full state or province:** Your state or province info.
* **City:** City name.
* **Organization:** The name of your organization.
* **Organization unit:** Organizational unit.
* **E-mail:** Your email address. This field is mandatory.
* **Common name:** The Common Name (CN), also known as the Fully Qualified Domain Name (FQDN). This field is mandatory.
* **Subject Alternative Names:** Add one or more subject alternative names (SANs). Note that because mobile Parallels Client don't support the Subject Alternative Name field, it is recommended to choose a common name that most mobile devices will be using.

Click **Generate** to generate the certificate. When done, the certificate will appear in the **Certificates** list with the **Status** column indicating **Self-signed**.

To view and modify certificate properties:

1. In the **Infrastructure** > **Certificates** view, click the certificate name.
2. In the right pane, review the certificate properties in the **Information** section.
3. In **Actions** section, you can enable or disable the certificate. You can also [export a certificate to a file](/landing/ras-mp-guide/v19-en-us/infrastructure/certificates/export-a-certificate-to-a-file.md). If you wish to delete the certificate, click **Delete**.
4. To modify some of the certificate properties, click **Properties** in the middle pane.
5. Click **Edit** in the upper left-hand corner to modify the settings if needed. You can change the certificate name and description and you can also change whether the certificate should be used for Gateways, HALB, or both.


---

# 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.parallels.com/landing/ras-mp-guide/v19-en-us/infrastructure/certificates/generate-a-self-signed-certificate.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.