> 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/configuration-client/site-installation/server-properties/web-services/changing-the-web-services.md).

# Changing the Web Services

This topic describes how you can replace the default Mobile Client and/or REST API web service TLS certificate with an alternative certificate, and how to update the certificate settings if the web service ports are altered.

* Replacing the web service certificate does not increase the security of the solution. Typically this is done to satisfy corporate policy.
* Altering the ports is only required to avoid collisions with other third party software, or to satisfy corporate policy.

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Changing the TCP ports that the web service listens on](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/web-services/changing-the-web-services.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Replacing the web service certificate with an alternative certificate](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/web-services/changing-the-web-services.md)

#### Changing the TCP ports that the web service listens on

1. Open the **Web Services** tab of the Server Properties in the Configuration Client, and enter the new data port numbers in the **Server Base Port** fields as appropriate.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-815d392f9487f03fc8446adef9b4c9ab5173dc7b%2Fwebservicestab_labelled.png?alt=media)

   **Note:** For Mobile Client, the web service data port is the one you specify here. The enrolment port is always that port plus one.
2. Click **Apply**.

   You should see the status update to reflect the port change. No further steps should be required in Command Centre, although it is likely you will need to reconfigure Windows Firewall, or any other third-party Firewall software, to allow the new ports.

#### Replacing the web service certificate with an alternative certificate

1. Open the **Web Services** tab of the Server Properties within the Configuration Client.
2. Click the **Manage Certificates** button for either the Mobile Web Service or REST API.

   The Manage Mobile Web Services Certificate dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a515f868cfc309c2ebc76125ff2ccea87d70db4b%2Fwebservices_managecertificatescrn.png?alt=media)
3. Select **Custom Certificate** and click **Import…**

   **Note:** See below for an explanation of the three certificate modes that are available on this dialog.
4. Use the file browser to find your PFX or P12 file containing the certificate and its associated private key, and then when prompted enter the password.

   **Note:** If you do not have a certificate in a PFX/P12 file, and instead have two separate files for the certificate and private key, you will need to convert them to a PFX/P12 file first. This can be easily done using OpenSSL or other tooling.
5. Click the **OK** button.

   The Manage Mobile Web Services Certificate dialog closes.

   **IMPORTANT:** The new certificate will not be saved to the database and will not take effect until you click the **Apply** button on the main **Web Services** tab, so it is likely you will wish to do this too.

**Note:** If you have existing devices running the Command Centre Mobile App, they will see the certificate change as a potential malicious attack and block connections to the server. You must re-enrol them. This does not affect the Mobile Connect App or Mobile Credentials.

### Certificate Mode explanations

<table><thead><tr><th width="211">Mode</th><th>Explanation</th></tr></thead><tbody><tr><td>Default Internal Certificate</td><td>The Default Internal Certificate is a self-signed certificate which is generated by Command Centre and stored in the database. It exists to provide a standard option for sites that don't need a custom certificate. The private key is protected by Command Centre's Database Encryption.</td></tr><tr><td>Custom Certificate</td><td>This lets you import your own certificate as per the instructions above.<br>The private key will be protected by Command Centre's Database Encryption.</td></tr><tr><td>External Certificate</td><td>An "External" certificate is loaded from the Windows certificate store rather than Command Centre's database.<br><br><strong>Note:</strong> If both the Mobile Client and REST API features are set to the "External" mode, then there is only one single external certificate which will be shared, but in either of the other modes they have distinct certificates.</td></tr></tbody></table>


---

# 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/configuration-client/site-installation/server-properties/web-services/changing-the-web-services.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.
