SOPS Pre-Purchase and Deployment Prerequisites

This page helps customers determine whether their environment is ready for SyncSign On-Premise Server (SOPS) before purchase. It describes what must be prepared, not how to install or configure the system.

Confirm Before Purchase

  1. Data source: Decide whether SOPS will connect to Microsoft 365, Google Calendar / Google Workspace, an on-premises Exchange Server, NextCloud / CalDAV, or a CSV URL.

  2. Server: Prepare a server or virtual machine that can run SOPS continuously, together with a valid SOPS license.

  3. Network: Ensure that SOPS can reach the data source and communicate with the SyncSign Hubs and Displays. Use a static IP address or stable domain name whenever possible.

  4. IT support: Assign an administrator who can configure account permissions, DNS, certificates, firewall rules, and OAuth applications.

  5. Room resources: If Displays will show meeting-room schedules, create the room resources in the calendar system and give the authorization account access to them.

Note

If SOPS will run on Amazon EC2, SyncSign does not currently provide a ready-to-launch AMI in AWS Marketplace. Your AWS administrator must be able to import the supplied SOPS virtual machine image and manage the resulting private AMI and EC2 infrastructure. See Deploy SOPS on Amazon EC2.

Requirements by Data Source

Data-source prerequisites

Data source

Confirm before purchase

Microsoft 365 / Exchange Online

SOPS has a publicly reachable HTTPS endpoint. Prepare a domain name, correct DNS records, a certificate issued by a trusted CA, and an inbound TCP 443 path to SOPS. Customer IT must be able to register a Web application in Microsoft Entra ID, configure the Redirect URI displayed by SOPS, create and maintain a Client ID and Client Secret, and grant the required Microsoft Graph delegated permissions. The authorization account must be able to enumerate and access every required room. SOPS cannot manually add a room that the account cannot enumerate. See Using Microsoft 365.

Google Calendar / Google Workspace

SOPS has a publicly reachable HTTPS endpoint. Prepare a domain name, DNS records, a certificate issued by a trusted CA, and an inbound TCP 443 path to SOPS. Customer IT must be able to create a Google Cloud project, enable the APIs required by SOPS, configure a Web application OAuth client and the Redirect URI displayed by SOPS, and maintain its credentials. The authorization account must be able to access the required calendars or room resources. See Using Google Calendar / Google Workspace.

On-premises Exchange Server

SOPS and Exchange can communicate through the LAN, VPN, or another routed network. Prepare the room mailboxes and Room List, a dedicated service account, and the permissions required to access the room mailboxes. Provide the Exchange address and account credentials. The Exchange data-source connection itself normally does not require a public domain or publicly trusted certificate. If Hubs connect to SOPS across the Internet, public access and firewall rules are still required. See Using Exchange Server.

NextCloud / CalDAV

SOPS can reach the CalDAV endpoint. Prepare a resource account, shared room calendars, the required calendar permissions, and an App Password. See Using CalDAV on NextCloud.

CSV URL

The CSV file is available at a stable URL that SOPS can reach continuously. The file contains a stable, unique Source ID; the hosting service remains running; and each Display can be mapped to the intended Source ID. See Using CSV URL.

Commonly Overlooked Requirements

Warning

For Microsoft 365 or Google calendar integration, allowing SOPS to make outbound Internet connections is not enough. The calendar provider must also be able to reach the SOPS authorization callback or notification endpoint. Customers must provide a publicly resolvable domain, a publicly reachable endpoint, a trusted HTTPS certificate, and an inbound TCP 443 path to SOPS.

  • Always use the complete OAuth Redirect URI displayed by the current SOPS Portal. Do not construct it from an older guide.

  • Plan a static IP address or stable domain name. Changing the SOPS address may prevent Hubs from reconnecting.

  • If the required network access, administrator permissions, or room access cannot be provided, contact SyncSign Support about alternatives before purchasing SOPS.

Pre-Purchase Checklist

  • The data source and SOPS deployment location are confirmed.

  • SOPS, the data source, Hubs, and Displays can communicate over the required network paths.

  • For cloud calendars, a public domain, trusted certificate, and inbound TCP 443 endpoint can be provided.

  • Customer IT can create and maintain the required OAuth application, Client Secret, or service account.

  • Room resources exist and the authorization account has the required access.

  • Owners are assigned for DNS, certificates, firewall rules, and account configuration.