I am working with AI Bridge in Milestone, and currently every time I set up an initial connection I need to generate and configure certificates from the VMS machine. This requirement applies even when I’m only testing from a developer machine, which makes the workflow cumbersome.
Is there any way to bypass or simplify this process, so that certificates don’t need to be generated on the VMS machine each time for development setups?
This is my
.env file
# The version of the AI Bridge to run
VERSION=“2.0.0”
# How the Bridge will be visible in XProtect as a Processing Server
BRIDGE_ID=“12355b21-5a25-4a1d-b6d2-f6e02c9b95b7”
BRIDGE_NAME=“AI Bridge from ajith”
BRIDGE_DESCRIPTION=“AI Bridge connecting IVA Apps with XProtect”
BRIDGE_WEBPAGE=“”
# XProtect endpoint and credentials (use https to connect with TLS)
VMS_URL=“https://10.5.1.43:443”
# VMS_USER=“admin”
# VMS_PASS=“password”
# Define these variables if your vms is not in the network domain (Check the docker-compose.yaml to uncomment relevant configuration)
[vms_ip](javascript:void(0); “vms_ip”)=“”
[vms_hostname](javascript:void(0); “vms_hostname”)=“”
# Master key that will encrypt VMS info at rest
MASTER_KEY=“”
# AI Bridge’s Kafka topics retention time in ms
KAFKA_LOG_RETENTION_MS=“300000”
# Encrypt communication with XProtect using TLS (uncomment both lines to enable)
# TLS_ENABLED=“true”
# TLS_SCHEME=“https”
# External IP address and hostname through which the AI Bridge services can be reached
EXTERNAL_IP=“10.212.134.201”
EXTERNAL_HOSTNAME=“ajith-OMEN-by-HP-Laptop-16-c0xxx”
# Path used to segmentate endpoints exposed outside of the AI Bridge running cluster.
EXTERNAL_ROOT_PATH=“/processing-server”
VMS_IP=“10.5.1.43”
VMS_HOSTNAME=“milestone”
# Network which AI Bridge containers are running on
AIBRIDGE_NETWORK=“aibridge_default”
ENABLE_IPV6=false