Understanding Bot agent communication channels with Control Room
The Bot agent uses various channels to communicate with Control Room. Relevant data is transferred directly and indirectly using communication channels such as loop-back interface, browser, plug-in, and WebSocket connection.
Browser to loop-back Interface
The browser to loop-back interface channel is used during initial Bot agent device registration and post-registration to check the current connection status to the Control Room. The loop-back interface uses HTTP unencrypted connection.
The following initial registration data is transferred over this channel:
- Control Room user token. This is accessible through developer tools on the browser.
- Control Room URL
- Proxy meta-data such as device id, proxy is configured or not, and uses authentication or not.
The following connection status data is transferred over this channel:
- Device ID
- Control Room URL
- Installation type such as system-level or user-level
- Proxy meta-data such as device id, proxy is configured or not, and uses authentication or not.
Browser to Control Room
The browser to Control Room channel is used by the browser to connect to the Control Room. The data transferred over this channel includes all Control Room web data. The browser uses HTTPS encrypted connection.
Plug-in to Bot agent named pipe
The plug-in to Bot agent named pipe channel is used to manage current logged in user session information and credentials if an authenticated proxy is to be obtained for the browser. The plug-in channel is protected by user permissions.
Bot agent to Control Room WebSocket
The Bot agent to Control Room WebSocket channel is used for all command and data transfer between the Bot agent and Control Room. Data transferred over this channel includes requests from Bot agent to Control Room, bot code transfer, password data, Control Room to Bot agent requests. Password data is payload encrypted with the device public key in addition to the TLS encryption of the channel.