Certificate examples

Simple single certificate example

Certificates have been generated at both HUB and Satellite locations. If the Certificate option is selected under Remote service validation in the Type dropdown, the public key versions are exported to each location.

Note: When using the basicHttp_Message_Certificate or wsHttp_Message_Certificate protocol, remote service validation is mandatory. The public key certificate of the remote location must be installed in the current location, and its subject name/thumbprint has to be provided in the Value textbox of the Remote service validation section.

• 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. Enter PROJ-XYZ-HUB-CERT in the Certificate field in the Client section.

At the Hub location in Admin, your inbound communication is received by service (or Hub, since the Hub acts as the service). Enter PROJ-XYZ-HUB-CERT in the Certificate field under the service section.

Since wsHttp_Message_Certificate is selected in this example, Remote service validation is mandatory. Install the public key of PROJ-XYZ-SAT-CERT at the hub location, and enter PROJ-XYZ-SAT-CERT in the Value field of the Remote service validation section.

The GlobalCommsSettings.config file looks like this.

At the satellite location, the entries are reversed.

Multiple certificate example (separate certificate for client and service)

A single private key certificate can be used both for client and service, except when using HTTPS protocol. HTTPS requires separate certificates for client and service. The following table shows examples of different certificates for client and service.

Note: At the current location, the public key copy of only the service certificate of the neighbor remote location is required.

Binding settings at HUB

Binding settings at SAT location

The GlobalCommsSetting.config file at hub

The GlobalCommsSetting.config file at sat