Certificate examples
- Last UpdatedFeb 07, 2022
- 2 minute read
Simple single certificate example
Certificates have been generated at both HUB and Satellite locations and the public key versions exported to each location.
-
Hub certificate is named PROJ-XYZ-HUB-CERT
-
Satellite certificate is named PROJ-XYZ-SAT-CERT
At Hub location in Admin, your out-bound communication is done from client, so PROJ-XYZ-HUB-CERT is entered in the Local field under the Client Certificate.

The same value is automatically entered into the Remote field under the Service Certificate, so you will actually see

The daemon Service manages in-bound communication, so in the Local field under the Service Certificate we enter PROJ-XYZ-SAT-CERT and again the Client remote field gets the same value.

The GlobalCommsSettings.config file looks like this.

At the satellite location, the entries are reversed.

Multiple certificate example
|
HUB |
SAT |
|---|---|
|
ACME-Global-cert-pc123 (private key) |
ANOTHER-cert-4-global-ukA (private key) |
|
ACME-Global-cert-pc432 (private key) |
ANOTHER-cert-4-global-uk20 (private key) |
|
ANOTHER-cert-4-global-ukA (public key) |
ACME-Global-cert-pc123 (public key) |
|
ANOTHER-cert-4-global-uk20 (public key) |
ACME-Global-cert-pc432 (public key) |
Binding settings at HUB

Note:
While the Remote field entries are auto-filled, they can be edited as required.
Binding settings at SAT location

The GlobalCommsSetting.config file at hub

The GlobalCommsSetting.config file at sat:

Note:
How the HUB - Client and Service binding entries mirror the SAT - Service and Client
binding entries as highlighted above.