The IVX Private Cloud supports Internet Content Adaptation Protocol (ICAP) integration to facilitate file scanning requests from ICAP Clients.
After deployment of the services using the Cloud Development Kit (CDK), the ICAP endpoints are available as URLs. We need to extract the host, port, and service name from these and configure the ICAP client accordingly.
Example CDK output:
"icap_tcp_endpoint": "http://nlb_dns_name:1344/ivx_scan", "icap_tls_endpoint": "https://nlb_dns_name:11344/ivx_scan" where ICAP server: nlb_dns_name Port: 1344 (TCP/ICAP) or 11344 (TLS/ICAPS) Service name: ivx_scan
These values should be be configured in ICAP client to communicate with the deployed ICAP Server.
ICAP Server configuration
ICAP configuration is managed through the config.json.
The following parameters can be configured, these must be modified before CDK deployment.
"icap_config": {
"respmod_enabled": true,
"reqmod_enabled": true,
"block_mode_enabled": true,
"block_mode_response_page": true,
"max_connections": 512,
"max_file_size_mb": 100,
"verdict_timeout_sec": 300,
"icap_is_tag": "ivx-service",
"log_level": 4
}