> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/milestone/milestone-integration-platform-mips-deep-dive.md).

# Integration Platform (MIPs) deep dive

Explain and resolve Milestone Integration Platform certificate-trust connection failures.

### Why the MIPs certificate failure happens

REST clients (like the MIPs client) connect to the Command Centre server over SSL, which requires the client to **verify the server's certificate** against the certificate authorities in its **Trusted Root Certification Authorities** store. The Command Centre server presents a **self-signed certificate** that is not in that store by default, so verification fails **silently**. There is no obvious error; the MIPs client simply does not connect.

![SSL handshake overview: the MIPs client (left) fails at the step where it must verify the CC server certificate](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-8a7c8f4177798c037f4318491e7e78ce33eda46b%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-03.png?alt=media)

A trusted website, for comparison, shows a padlock because its certificate chains up to a trusted root:

![Chrome showing a secure padlock for a trusted website (google.com)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0bc0d757f575670697493d38b269317a59fe7152%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-02.png?alt=media)

![google.com certificate properties (General tab)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a43eaa7b1ef75b3fe07e9c129b9758461d4cf663%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-11.png?alt=media)

![Certificate "Certification Path" tab showing the trust chain up to a root CA](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fce8d7311b4eec1800e082171168cca92ab3d0f7%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-05.png?alt=media)

![The root CA present in the client's Trusted Root Certification Authorities store](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b11da0c83cb09fd27559e27caff15ccfeb4ad4d0%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-08.png?alt=media)

The Command Centre server, by contrast, shows "Not secure" because the CC REST certificate is not trusted by the client:

![Chrome "Not secure" warning connecting to the CC server REST endpoint](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-9ee7309b48fd870dd1145e8ac615362b8d5bd401%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-01.png?alt=media)

### Export the CC REST certificate and import it on the client

![Server Properties → Web Services: the REST API "Manage Certificates" button, the CC-server-side starting point for exporting the certificate](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a07666ad770a50b0ecbbdbab48c0c561147c3dd7%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-04.png?alt=media)

![The "Manage REST API Certificate" dialog on the CC server: Default Internal Certificate selected, "View" highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ece91e691fa6e70d003269caae7d1011f9c69da3%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-07.png?alt=media)

![On the MIPs client: certlm → Trusted Root Certification Authorities → All Tasks → Import, to import the exported CC certificate](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fa3627963167c5c75d70efcf6e849a4fbbb67dd0%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-10.png?alt=media)

![The Gallagher Command Centre Server certificate now present in the client's Trusted Root Certification Authorities store (valid to 2040)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ce6caa04d8ef38506e30c21367e9b024845dd999%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-09.png?alt=media)

![Success: a secure padlock when connecting to the CC server after importing the certificate](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1205d6184c76ecd7a55975296f090b2cbc77b82d%2FSECHUB-INT-MILESTONE-MIPS-DEEPDIVE-06.png?alt=media)

{% hint style="warning" %}
When testing, manually **terminate any previously active REST sessions** on the Command Centre server first. A still-open session can make a fresh test look like it failed when it has not.
{% 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://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/milestone/milestone-integration-platform-mips-deep-dive.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.