Yes, the Kore.ai Bots Platform includes our Cloud Connector, an agent that runs behind your firewall within your company Intranet or perimeter network (DMZ) to provide secure data exchange between the Platform (when run in the cloud) and your on-premises applications.
How it works: The Platform contacts the Platform’s Connector Gateway with a bot request. The Connector Gateway relays the request to the Connector Agent, which is installed and securely configured in your on-premises Intranet or DMZ to interact with your bots applications. Response from your applications are sent back through the Connector Gateway to get to the Platform, and processed.
Optionally, you can enable your on-premises applications to push data, for example, alert messages, to the Platform using Webhooks. For bots that are being deployed in 3rd party channels like Facebook Messenger, the Platform also leverages the maximum encryption protocols available when transmitting bot-based data to and from other communication channels. Other features of the Kore.ai Bots Platform approach to the cloud connector include:
- Streamlined Installation: Step-by-step instructions are available for downloading, installing, and configuring the Platform Connector Agent across your on-premises infrastructure.
- Persistent TLS Connection: A Transport Layer Security (TLS) tunnel connection is established between the Connector Gateway (integrated with the Platform server) and the Connector Agent.
- Automatic Re-connectivity: The Platform’s Connector Agent maintains a persistent connection with the Connector Gateway. If network connectivity fails, the Connector Agent re-establishes a new connection automatically.
- Comprehensive Audit Logging: The Connector Agent writes an audit log entry whenever an administrator changes any critical configuration settings, such as virtual mappings, allowed resources, etc.
- Scalable Load-Request Handling: The Connector Agent starts in cluster mode with the number of workers equivalent to the number of CPUs.
- X.509-Based Authentication: TLS communication is established by the Connector Gateway issuing X.509 certificates to the Connector Agent.
- Flexible Access Control Support: Administrators can specify a virtual hostname and port for an on-premise system accessed by the Connector Agent. A whitelist can also be used to specify accessible resources or paths.
- No Firewall Changes: The Connector Agent can be installed in the DMZ or in an inner network zone without changes to an external firewall provided port 80 and 443 are open.