This article will go through the requirements to receive communication back to the CL Connect server for any Event Notifications that are to be configured.


In order for the API service to communicate with CL Connect, a public-facing DNS must be created. As this process varies greatly between DNS providers, we are unable to provide instructions for this step.


An SSL certificate, signed by a valid CA, will also need to be installed on the server for CL Connect.


NOTE: A wildcard certificate is suitable to use for CL Connect.


IIS Bindings:

1. Once the public-facing DNS and SSL certificate are in place, the IIS bindings for CL Connect need to be updated to allow this incoming communication.


2. Bring up IIS and navigate to Default Web Site, or whatever the website is titled for the instance of CL Connect.


3. The bindings can be access in two ways as shown in the picture below. Either right-click on Default Web Site and select Edit Bindings..., or select Default Web Site and under the Actions menu on the right there is a link for Bindings...



4. Click on the Add... button.



5. Change the Type: to https from the dropdown menu options.



6. Notice this will change the port to the default for https of 443. If the port is going to be different than the default, or if port 443 is already in use on that server this needs to be changed here.



7. Add the Host name: and select the installed SSL certificate from the dropdown menu.



8. Click on the OK button.



9. Click on the Close button.



10. Click on the Browse "Host Name" :443 (https) option under the Actions menu on the right.



11. The result should be the CL Connect landing page.



Next Steps: Verify the Firewall Rules for the server are updated to keep this server secure: Firewall Rules