Knowledge Base
Sectigo Orchestration Gateway (SOG) installation guide for Windows
Overview
By the end of this guide, you will have a Sectigo Orchestration Gateway (SOG) installed on Windows, registered with Sectigo Certificate Manager (SCM), and confirmed as connected. The guide covers the prerequisites, downloading the Microsoft Installer (MSI) package and the installation token from SCM, running the installer, verifying the installation, initializing a keystore using the Command Prompt (CMD), validating the gateway, and common troubleshooting. The install sequence should be confirmed against your SOG version, as installer screens can vary by release.
1. Prerequisites
-
Windows Server, or Windows 10 or later.
-
Access to Sectigo Certificate Manager (SCM).
-
The Sectigo Orchestration Gateway installer (Microsoft Installer, MSI package).
-
An SCM installation token for authentication.
-
Local administrator privileges.
2. Download the SOG installer
-
Log in to the SCM portal.
-
Go to Integrations > Orchestration Gateways.
Figure 1. Sectigo Certificate Manager navigation with Integrations expanded and Orchestration Gateways selected.
-
Click the Add icon to add an orchestration gateway.
Figure 2. Orchestration Gateways list in SCM; gateway names and identifiers are redacted.
-
Enter a name for the gateway and click Next.
Figure 3. Add Orchestration Gateway dialog with the gateway Name field.
-
Copy the installation token and download the Windows MSI installer.
Figure 4. Gateway details: the installation token is redacted; the Windows MSI, Linux RPM, and Linux DEB download links are shown.
3. Install SOG on Windows
-
Copy the MSI installer to the Windows server and double-click it to start setup.
-
Accept the end-user license agreement and click Next.
Figure 5. Sectigo Orchestration Gateway setup wizard showing the end-user license agreement.
-
When prompted, enter the SCM installation token.
Figure 6. Setup wizard Registration Token screen with the token entry field.
-
Continue through the wizard until installation completes, then click Finish.
4. Verify the installation
-
Go to the installation directory (for example, C:\Program Files\Sectigo Limited\SectigoOG).
-
Confirm the sectigo-og executable exists.
5. Initialize a keystore (required)
The gateway will not function until a keystore is initialized.
-
Open Command Prompt (CMD) as Administrator.
-
Go to the SOG install directory:
cd "C:\Program Files\Sectigo Limited\SectigoOG"
-
Check existing keystores:
sectigo-og.exe keystore list
Figure 7. Command Prompt output of keystore list showing one PKCS#12 keystore; the keystore name is redacted.
-
Add a new keystore and follow the prompts to configure it. Replace <type> with a keystore type (jks for a Java KeyStore, or p12 for a PKCS#12 keystore):
sectigo-og.exe keystore add <type> --name <name> --password <password>
Figure 8. Keystore add command syntax with placeholders for type, name, and password.
6. Validate the installation
-
Run the version and status check:
sectigo-og.exe info
Ensure no errors are returned and the status is connected, then check the SCM portal to confirm the gateway is registered.
Figure 9. Command Prompt output of sectigo-og info showing status connected; the hostname is redacted.
Figure 10. Orchestration Gateways list showing the gateway with a Connected status; account name and identifiers are redacted.
7. Common issues and troubleshooting
-
Invalid token: verify the installation token from SCM.
-
No keystore: initialize a keystore before use (see step 5).
-
Permission errors: run Command Prompt (CMD) as Administrator.
-
Connectivity issues: ensure outbound access to your SCM endpoints on TCP port 443.
Need assistance?
Contact our team for help with your purchase or issuing your certificate.
Live chat
Click the button below or click "Chat with an Expert" to start chatting with us now!
