Select the HTTPS protocol

Select the HTTPS protocol using Global Binding Configuration

1. Specify the globalcommssetting path in admindwcf.exe.config and globalwcfclient.config files in Administration, Global, E3D Design etc.

   

2. Open Administration and in Settings menu click Global Binding Configuration. For the local hub to product communication any protocol can be used.

3. In the Binding Settings window, https protocol for communication between two locations (demon to demon) over the WAN/inernet is required. Select either BasicHttp_Transport_Certifcate or WsHttp_Transport_Certificate to enable HTTPS.

   

4. Enter the client certificate subject (common name) or thumbprint value in the Certificate field of the Client section of the Binding Settings window.

5. Enter the service certificate subject value in the Certificate field of the Service section of the Binding Settings window.

   Installing the public key copy of neighbor location’s service certificate is optional. It is an additional security measure. Generally, the service certificate’s common/subject name is same as the host name in the address used for global. If it is different, an identity mismatch error occurs. To resolve this, use remote service validation. For more information, see Remote service validation.

   Note: A single private key certificate per location can’t be used when using HTTPS. Use two certificates per location one for client and another for service.

   At hub:

   

   At satellite:

   

6. Select Apply and perform a save.

7. Start the global demon to see the endpoints demon. Verify it contains one HTTPS endpoint.

   

8. Set up the service certificate.

   Obtain a client certificate based on the Client authentication template and install in on your machine.

   See Server certificate setup for HTTPS for more information.