> 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/cloud-services/command-centre-mobile-client/configure/mobile-client-connection-options-signe.md).

# Mobile Client connection options: Signed Token or TLS client certificate

Choose Signed Token or TLS client certificate authentication for Mobile Client connections.

The Mobile Client can connect using one of two methods. The right choice depends on whether the deployment uses a reverse proxy.

| Option                     | Reverse proxy?                                                                 | Security                 | Notes                                                                |
| -------------------------- | ------------------------------------------------------------------------------ | ------------------------ | -------------------------------------------------------------------- |
| **Signed Token**           | **Required** for Reverse Proxy mode                                            | Less secure than TLS     | Works for any other mode too                                         |
| **TLS Client Certificate** | **Cannot** be used through a reverse proxy (the proxy cannot open the packets) | Recommended, more secure | Gallagher's default recommendation outside reverse-proxy deployments |

***

🔗 **Related**

* [Reverse Proxy Connection Issues](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-reverse-proxy-connection.md). Why Signed Token is required through a proxy.
* [Unable to add a Mobile Client](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-unable-to-add-a-mobile-c.md). Initial connection setup and ports.


---

# 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/cloud-services/command-centre-mobile-client/configure/mobile-client-connection-options-signe.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.