> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/bmc-user-guide/security/managing-certificates.md).

# Managing Certificates

Using a trusted SSL certificate is essential for securing all communication with your BMC. By default, the BMC uses a self-signed certificate, which is what causes the "Your connection isn't private" warning in your browser. To eliminate this warning and establish a fully secure connection, you should replace the default certificate with one signed by a trusted Certificate Authority (CA).

This chapter guides you through the process of generating a request for a new certificate and installing it on the BMC.

## **Generating a Certificate Signing Request (CSR)**

The first step to getting a trusted certificate is to generate a Certificate Signing Request (CSR). This is an encoded block of text containing information about your organization and the BMC's domain name, which you will submit to a CA.

1. In the sidebar menu, navigate to **Security and access** > **Certificates**.
2. Click the **Generate CSR** button.
3. Fill out the form with your organization's details. The most important field is the **Common Name**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd30c24RiuIUb6hpqW9Q9NeVZfXkYx4XYTqu7T4xY8C5DHbG-Ftvrob7Crv4PJX-9k38Z5cYNunMOK2gLn1V9tSbTzGAdKrTT3bhR3xkg2YbhluorHJJN0jyhaLzNN1g41pqcc1SA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

* **Common Name (CN)**: This **must** be the fully qualified domain name (FQDN) or IP address that you use to access the BMC in your browser (e.g., `bmc-server-01.yourcompany.com`).
* **Company name / unit**: Your organization and department name.
* **City / State / Country Code**: Your organization's location.
* **Key Pair Algorithm**: Choose the desired encryption algorithm (e.g., RSA-2048).

4. Click **Generate CSR**. A `.csr` file will be generated and downloaded to your computer.<br>

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdzArzdP4uhQiUCNjaGU22YK3iHgyQ1QjR0g6Vp7wKISK0w4fnPwsVUj69yjmwmldJ1IL703b_X1vzrylfk6mNbIt3diBmGrRQa93orWuMz1VgEMtJBMwA65poT9STsZJwqjvpCJA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

## **Uploading and managing SSL certificates**

Once you have submitted your CSR to a CA (like Let's Encrypt, DigiCert, etc.) and they have sent you back a signed certificate file, you can install it on the BMC.

1. On the **Certificates** page, click the **Add new certificate** button.
2. In the popup window, select the **Certificate type** (e.g., `HTTPS Certificate`).
3. Click **Add file** and select the certificate file (`.crt` or `.pem`) that you received from your CA. You may also need to upload the private key file (`.key`) if it was generated separately, and any intermediate CA certificates.
4. Click **Add** to upload and install the certificate.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdXAOr9r483-V7P1xUvMdkDwMHFlf3y_xB5-dvWQJJjn6b0WlYfLf7Snqc9dDktNiJLFqADgKw7SFR8a5-lQixswKNZt9yWOoGmRl0plhXubZ4LNVa2b_oQYaBkiJXt-9BGGEoA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

After the new certificate is installed, the BMC's web service may restart. You should then close your browser, reopen it, and navigate to the BMC's address. You should now see a lock icon, indicating a secure, trusted connection with no security warnings.

{% hint style="success" %}
**Best Practice: Use a trusted CA**

While self-signed certificates provide encryption, they don't provide trust. Users will always see a security warning. Using a certificate from a trusted internal or public CA is a critical step for a production environment. It ensures that users can verify they are connecting to the legitimate BMC and not a malicious imposter.
{% 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://doc.engenius.ai/bmc-user-guide/security/managing-certificates.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.