> 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.md).

# 6. Salto Server Connection

### Introduction

If your site is not able to immediately upgrade to HTTPS + Salto Native integration (encrypted communication is desired), it is recommended to setup a secure tunnel between the Salto server and Command Centre server.

### Procedure

This procedure is split into three parts, as follows:

<details>

<summary>1. Changing settings in Salto Space</summary>

Before changing connections to HTTPS in Command Centre Configuration Client, settings from the Salto server side need to be changed, as follows:

1. Log on to Salto Space.
2. Select **System** > **General options** > **SHIP**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-556d9873285ebcc7bd2499d861eabd51e6728238%2Fsaltospace_shiptab.png?alt=media)
3. Change Transport Protocol to **HTTP(S)**, and select "Custom" from the **Authentication** drop-down list.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-03d7cd4e15a81e38d7a148caeab9829310c75ed8%2Fsaltospace_httpsoption.png?alt=media)
4. Create a unique key in the **Key** field, then re-type it in the **Confirmation** field and click **Save**.

   **Notes:**

   * This key is based on a custom token that a client provides when making HTTP requests. API keys are supposed to be a secret that only the client and server know.
   * Once the key is populated, it won’t be able to see anymore from Salto Space.
5. Double-click the **ProAccess SPACE Configurator** icon on your desktop.
6. From the **Service Properties** tab, click the **STOP** button to stop the Salto services.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-afcc35e88cfa8e8d51c0dc9fc5d7398bf60e417c%2Fsaltospace_serviceproperties.png?alt=media)
7. Select the **Service ports** tab and tick "Use HTTPS"checkbox.
8. Choose the correct certificate from the drop-down list.

   **Note:** Please consult your IS department for the certificate to be installed.

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

   **Notes:**

   * If you skip Steps 5 - 7, when Command Centre changes to HTTPS connection, the following warning message will display:

     ![](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)
   * If the certificate has changed from the Salto side, the Command Centre will lose connection with the Salto Server.
9. Click the **Start** button to start the Salto services.
10. Click **VERIFY** for Salto authentication Port to check your port is working, and then click **SAVE**.
11. Return to Salto Space and select **System** > **General options** > **Users**.
12. Within the 'Settings' section, select the **Discarded openings are also included in the key's auditor** check box.

    This setting is required for unauthorised events with offline doors to be raised in Command Centre.
13. Within the 'Tracks of user key section', Gallagher recommends ensuring the **Wiegand code** checkbox is selected and **Profile code** is selected.

    This is required for when you create third party doors using UBOX4000 or other wired door controllers.
14. Click **Save**. If a Warning window displays, click **Yes**.

</details>

<details>

<summary>2. Changing to HTTPS connection in Command Centre</summary>

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)

</details>

<details>

<summary>3. Enabling Salto-Native Users Mode</summary>

1. Click the **Calendar Options** tab.

   This tab allows you to select three special Day Categories and a Calendar which will be reflected in Salto.

   **Note:** If you have enabled Native Mode, once Day Categories and Calendars are selected in Command Centre they are reflected in Salto.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-316afb1ce669ae0e370bf9bc78283324417c30c9%2Fsaltoserver_calendaroptionstab.png?alt=media)
2. The **Special Day Categories** section allows different access times to be configured for special days so that cardholders can have different access depending on the day.

   Select the appropriate options from the **Holiday**, **Special Day 1** and **Special Day 2** drop-down lists.

   **Note:** Each drop-down list shows the available Special Day Categories and Calendars within an operator’s divisional privileges.
3. Select the appropriate 'Calendar' from the drop-down list to be used as the **Default SALTO User Calendar**.

   **Note:** If **Calendar** is not selected, the system will use the "Default Calendar" as the Salto User Calendar.
4. Click **Apply** to save your changes.
5. Once HTTPs communication is established, in Configuration Client, click the **Enable SALTO Native Users** button on the **Settings** tab of the Salto Server properties.

   **Note:** Salto Native license is required to Enable SALTO Native Users.

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

   The following prompt displays:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-37fc18032f7f739701260d4ace7d3e1c32976984%2Fsalto_warningmessage_nativeusers.png?alt=media)
6. Click the **Yes** button.

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

   After moving to "SALTO Native Users" mode:

   * The **Enable SALTO Native Users** button is disabled and an event is generated.
   * A "GallagherCommandCentre" partition is created in Salto Space which will be used to separate Command Centre created/used items from other items in Salto. The partition protects all Command Centre used Salto Users, Access Levels, Cardholder Timetables and Calendars in Salto Space. It is important to leave this data untouched because they are managed by Command Centre. Any Salto Space operator other than the default system operator should be restricted from accessing the "GallagherCommandCentre" partition.

     How long it takes to sync cardholders and access privileges is dependant on the number of cardholders and Salto doors, (e.g. up to 10,000 cardholders can take up to 15 minutes).
   * The Salto Server status will be changed to *"SALTO Native Users"* on the **Status and Overrides** tab.

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

     If the site is updated from Legacy to Salto Native Users mode, then the status message will display if there are any Salto Legacy User(s) remaining, and how many.

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

</details>


---

# 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.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.
