> 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/integrated-systems/salto-lock-interface/space-installation-instructions/6-salto-server-connection/2-changing-to-https-connection-in-command-centre.md).

# 2. Changing to HTTPS connection in Command Centre

1. In Configuration Client, click **Configure** from the menu bar, then **Salto**.

   The **Salto** List Window opens.
2. **Right click** on the Salto Server and select **Properties**.

   By default the **General** tab displays.
3. Click the **Settings** tab.

   How the screen looks depends on whether this is a new or an existing site.

   <table><thead><tr><th width="126">If...</th><th>then...</th></tr></thead><tbody><tr><td>a new site,</td><td><p><strong>Encrypted (HTTPS)</strong> is the default "Transport" connection.</p><p>If your site chooses to use Salto Native Mode, settings from the Salto server side need to be changed.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-88d44379fc563729eb6d7d308da9ff5f3df48c2a%2Fsaltoserver_settingstab_newsite.png?alt=media" alt=""></p></td></tr><tr><td>an existing site,</td><td><p>there are two "Transport" options to choose from, i.e. <strong>Legacy (STP)</strong> and <strong>Encrypted (HTTPS)</strong>.</p><p>Select the appropriate "Transport" radio button:</p><ul><li><p><strong>Legacy (STP) Transport with Legacy Mode:</strong></p><p>This option is available for STP (TCP/IP) connection, however it is recommended to use the Encrypted (HTTPS) option to secure communication.</p></li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5631f859a633df56490deeb9e8c8fead4644ac7f%2Fsaltoserver_settingstab_existingsite1.png?alt=media" alt="" data-size="original"></p><ul><li><p><strong>Encrypted (HTTPS) Transport with Legacy Mode:</strong></p><p>If your site chooses to use Salto Native Mode, this option must first be selected. Before changing connections to HTTPS, settings from the Salto server side need to be changed.</p></li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8391568e82a3a7a902cc6466ecf8e5822a0d0877%2Fsaltoserver_settingstab_existingsite2.png?alt=media" alt="" data-size="original"></p><ul><li><p><strong>Encrypted (HTTPS) Transport with Native Mode:</strong></p><p>After the site enabled Native Mode, the Server Connection page will still display the incoming port so that existing Legacy Mode cards can use the STP connection. Completing Native Mode card migration will allow this port to be closed.</p></li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1bcba50b60504d67669d430a97d79f2ff042dde2%2Fsaltoserver_settingstab_existingsite3.png?alt=media" alt="" data-size="original"></p></td></tr></tbody></table>
4. The single Salto Server Command Centre item has the following properties which are valid for the Server only:
   * **Address** of Salto Server (default = empty). This needs to be changed to the Server name or IP Address for the Server running the Salto application, if the Salto Server does not reside on the same PC as the Command Centre Server. It can take up to approximately ten seconds for the Salto server to come online after configuring or re-configuring the Name / IP-Address.
   * **Port** is the port for outgoing requests to Salto Server (Default to 8100).

     The port comes from the "SALTO authentication" field on the **Service Ports** tab in the ProAccess SPACE Configurator.

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b98d4e7a857b66f379020f5ac67e5931fee138bd%2Fsaltospace_authenticationfield.png?alt=media)
   * **Incoming Port** is for legacy Salto card updating its access information from Command Centre. Native Salto cards don't require this. Command Centre will automatically open or close this connection according to whether or not legacy cards exist. Communication on this port is not encrypted (Default to 8096).
5. Type or paste the **SHIP Key** that you created for Salto Space and click the **Apply** button.

   Refer to Steps 3 and 4 of **1. Changing settings in Salto Space** (earlier).

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

   Command Centre is now connected to the Salto Space Server.

   **Notes:**

   * Clicking the **Show** button will display the key that you have entered. Clicking the **Apply** button changes the text back to X’s and the Show button is enabled again. An operator event is also logged.
   * A "SALTO Native Users" section displays, and once HTTPS connection is successfully created, the Legacy (STP) connection is still available to switch back to. However, the **Enable SALTO Native Users** button will be disabled if the **Legacy (STP)** radio button is selected.

     **Note:** Existing sites need to be licensed for Salto Native User Mode for the "SALTO Native Users" section to display.

     Once HTTPS connection is established, if you want to change the Server Connection settings, (i.e. IP Address, Port and SHIP Key), they must be changed in Salto first, and then replicated in Command Centre. The following warning message will display if any changes are made:

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


---

# 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/integrated-systems/salto-lock-interface/space-installation-instructions/6-salto-server-connection/2-changing-to-https-connection-in-command-centre.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.
