> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/2025.4/getting-started/accept-certificate-authority.md).

# Accept Certificate Authority

In the current release of <code class="expression">space.vars.product\_name</code> , a few services are configured with self-signed certificate. You must trust the certificate by accepting the self-signed certificate for proper operation of these services.

Following services require you to trust the certificate:

1. Image Library Service - You need to trust the certificate before you can upload any Images using <code class="expression">space.vars.product\_name</code> UI or API.
   1. When using the OpenStack CLI, you can use `--insecure` option to upload images to the Image Library Service without trusting the certificate.
2. Kubernetes Service - You need to trust the cluster endpoint certificate for each Kubernetes cluster that you create, before you can view any cluster specific data in the <code class="expression">space.vars.product\_name</code> UI.

To accept the certificate:

1. Click on the link in the UI where you see a notification that says "Action Required: Trust Certificate"
2. The link will open in a new tab. Expand on the "Advance" option in the tab and proceed to click on the link to trust the certificate.
3. Note that in some cases you may need to change the security settings for your browser before you can trust the certificate.


---

# 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.platform9.com/private-cloud-director/2025.4/getting-started/accept-certificate-authority.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.