Sage 50 & Compleat connector security

This article tells you everything you need to know about how Sage 50 integrates with Compleat using our secure connector.

Installation

Our Sage 50 connector is installed locally on your LAN via an MSI installer.

It’s then configured using a secure PIN number unique to your Compleat account, which the Compleat Administrator in your company can access via the Compleat web front-end.

During configuration, local connection details are applied to the connector, which are used to communicate with Sage 50 using the SDO & ODBC integration capabilities supported by Sage.

These connection details will include a Sage username & password. We recommend that you set up an integration account in Sage 50 specifically for this purpose. This information is only ever stored in the locally-installed files, & will never leave your LAN.

Establishing a connection

The connection is established outbound from your network, meaning no firewall rules need to be put in place (unless you have the most restrictive corporate firewalls in place, & outbound communications may have been blocked).

Communicating with Compleat

Once the connector is running, it communicates with Sage 50 using SDO & ODBC on the LAN. For communicating back to Compleat on the cloud, the connector opens up a persistent outbound connection to Compleat.

Compleat & the connector can communicate bidirectionally to exchange information. All data exchanged on this communication is secured & encrypted using TLS.

The connector also periodically calls API endpoints in Compleat, primarily for initial registration & heartbeats. These are HTTPS API calls, encrypted using TLS 1.2.

Compleat will never attempt establish an inbound connection to your LAN.