Gravatar for

Question by esequielp, Jan 19, 2017 12:37 PM

SSL Certificates for multiple bindings


We have an IIS site with different bindings. Each binding is aimed for a different Sitecore site. After upgrading to the latest version of Coveo (Dec 2016), we have issues connecting to the Coveo rest api from bindings which name is not the same of the iis site name.

I went through the process of creating the self signed certificate for the main site and it went well but you cannot add different certificates to each binding in IIS. This happens in our local environments. Is there any way to bypass this security check?


  • IIS site name: coveosite
  • Bindings:
    • coveosite port 443
    • coveositefrench port 443

Both uses the same SSL certificate created for coveosite. coveosite works OK. coveositefrench cannot connecto to coveo rest api due to issues with the SSL certificate and its validation.

Let me know if the point is clear.

0 Reply
Ask a question