Coveo for Sitecore 5 is now available!

Securing the Admin Service

On-Premises only

The Admin Service is a service installed along with Coveo Enterprise Search (CES). It provides an API to the CES Administration Tool, which allows the Coveo Search Provider to automate various tasks through programming (creating sources, editing a security provider, etc.). If you install the Admin Service and CES on a dedicated server - that is, on a server different from Sitecore - we highly recommend that you enable secure communications. Here are the necessary steps.

Step 1: Enable Admin Service Security

  1. When installing CES, in the Configuration screen, choose Configure next to Admin service security.

    Coveo for Sitecore (April 2017)

    You can secure the Admin Service or change its settings directly from the Control Panel in Sitecore (Control Panel > Coveo Search > Configuration > Admin Service Connection).

    Coveo for Sitecore (April 2017)

    If you have already installed CES without the Admin Service feature (or without a secure Admin Service), re-run the installation package and choose Modify. You’ll have access to the same screen as above. For CES releases prior to August 2015, it may be necessary to remove the Admin Service in a first step, and then add it again to enable it and be able to change its settings.

  2. In the Coveo Enterprise Search Admin Service Security Options screen, select Enable Coveo Enterprise Search AdminService security.

  3. In the same screen, click Configure next to Configure credentials for the Admin Service.
  4. In the Create the access credentials for the CES Admin Service screen, enter the credentials that will be used to secure the Admin Service.

  5. Back in the previous screen, click Configure next to Configure a certificate for the Admin Service.

  6. In the Create a certificate to secure the Admin Service screen, enter the settings that will be used to generate a certificate:
    1. CES Server domain name: enter the FQDN of the CES server or an alias that you’ll be able to refer to using your hosts file later on (e.g. ces-server.acme.com or SVR-CES).

      This value will be in the Subject field of the generated certificate, thus representing the CES server host name. This implies that you’ll need to use this host name throughout the steps of the Configuration Wizard.

    2. Private key password / Confirm password: enter the password that will be used to protect the certificate private key.

    3. Port number: enter the port number used by the Admin Service. By default, it’s 443.

    4. Export path: enter the path where the certificate’s .pfx file will be exported.

  7. Proceed with the rest of the installation steps.
  8. Retrieve the generated certificate file (.pfx) and keep it for the upcoming configuration steps in the Coveo for Sitecore Configuration Wizard.
  9. Validate that the Admin Service URI is accessible in a web browser (typically https://localhost/AdminService).

Step 2 - Validate That the Admin Service Is Now Secure

When loading the Coveo Diagnostic Page of your Sitecore instance, all components should be in the Up & running state, especially the Admin Service.

Troubleshooting

  • Problem: port 443 is already used by another application or service.
  • Solution: you can easily change it via the file Coveo.CES.AdminService.exe.config that’s located in the bin folder of CES. There’s a section called appSettings. You can change the port there. Remember to restart the service after this change. 

    <appSettings>
      <add key="port" value="443" />
    </appSettings>
    
  • Problem: the Admin Service isn’t accessible via its URL.
  • Solutions:
    • Make sure that the Admin Service is started.
    • Make sure that a certificate is bound to the port of the Admin Service.
    • Make sure that no error appears in the Coveo Diagnostic Page. A common error is: “Could not establish trust relationship for the SSL/TLS secure channel with authority.” It means that the Sitecore server doesn’t trust the certificate of the Admin Service/CES server. To diagnose this issue, you can enable the System.Net traces in the web.config of your Sitecore instance as explained in My Favorite System.Net trace configuration file. You should be looking for errors related to certificates and trust in the generated .log file.
  • Problem: you see the invalid token.
  • Solution: it means that the token that your Search Provider has is invalid. You’ll have to restart Sitecore to get a new one immediately.
Recommended Articles