---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Connect the agent to the MID Web Server using TLS

# Connect the agent to the MID Web Server using TLS {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Connect the agent to the MID Web Server to enable configuring mTLS on your MID Web Server and agent.

## Before you begin

Ensure that you have installed the .pem file and set up the MID Web Server. For details, see [Set up the MID Web Server with a .pem file](https://www.servicenow.com/docs/s7QW1k_oEpnG6G7LlsFJzQ "Install the .pem file into the MID unified keystore and set up the MID Web Server to enable configuring mTLS on your MID Web Server and agent.").  
Note:  
This procedure includes commands for both CentOS 7/Linux and Windows Server environments. Select the commands relevant for your host operating system. If working with another Linux distribution, adapt the commands as needed for your specific OS.

Role required: agent_client_collector_admin

## Procedure

1. In a Linux environment:
   1. Add the labcacert.pem file to your agent host's trust store.  

          sudo cp -a /<path>/<to>/labcacert.pem /etc/pki/ca-trust/source/anchors/;
          sudo update-ca-trust extract
          openssl verify /<path>/<to>/labcacert.pem

      The generated output is: `/<path>/labcacert.pem: OK`
   2. Configure the acc.yml file to use TLS.  
      1. Set the insecure-skip-tls-verify property to `false`.
      2. Set the backend-url property to use the MID Server's FQDN.

      {#agent-mid-connect__ol_o4t_g4t_bkc}

          backend-url="wss://<mid server fqdn>:<mid web server port>/ws/events"

   3. Restart the agent.  

          systemctl restart acc;

   4. Verify in the logs that the agent is connected to the MID Server.
   {#agent-mid-connect__substeps_linux_all}
2. In a Windows environment:
   1. Add the labcacert.pem file to your agent host's trust store by importing it into the Windows Certificate Store.  

          certutil -addstore -f "Root" <path>\labcacert.pem
          openssl verify -CAfile <path>\labcacert.pem <path>\labcacert.pem

      The generated output is: `<path>\labcacert.pem: OK`
   2. Configure the acc.yml file (`C:\ProgramData\servicenow\agent-client-collector\config\acc.yml`) to use TLS.  
      1. Set the insecure-skip-tls-verify property to `false`.
      2. Set the backend-url property to use the MID Server's FQDN:

             backend-url:
              - "wss://<mid server fqdn>:<mid web server port>/ws/events"

      {#agent-mid-connect__ol_mzd_xrt_bkc}
   3. Restart the agent using one of the following methods:  
      * Command line:

            net stop AgentClientCollector
            net start AgentClientCollector

      * Services app: Select and hold the Agent Client Collector entry and select Restart.
      {#agent-mid-connect__ul_pwc_lf5_bkc}
   4. Verify in the logs that the agent is connected to the MID Server.  
      Logs are located at: `C:\ProgramData\ServiceNow\agent-client-collector\log\acc.log` (or the location set by the log-file configuration parameter).
   {#agent-mid-connect__substeps_windows_all}

## What to do next

[Configure mTLS authentication for a MID Web Server](https://www.servicenow.com/docs/0wySALLDemGgtwLX~IeHNQ "Enhance security in your MID Web Server extension by enabling mTLS authentication.").