Replicant Pen Test Page

This page demonstrates the integration of the Replicant AI chat widget. The widget code is loaded from our public.stage.replicant.ai, and the widget theme config.json is loaded from the tenant's bucket, in this case dr-chat-f1b678c1.public.stage.replicant.ai.

Technical Details:

Widget Delivery: Widget JavaScript is served from https://public.stage.replicant.ai/chat/v2/js/widget.js
iframe HTML: The chat widget runs in an iframe loaded from https://public.stage.replicant.ai/chat/v2/index.html
Theme Configuration: The base theme is set on https://public.stage.replicant.ai/chat/v2/config.json and can be overridden by the tenant's config.json file.
Customer Configuration: Configuration is passed via the window.replicant object and includes the customer identifier (tenant slug + first part of the UUID, to prevent bucket enumeration) and deployment ID (configuration stored in Broker's database).
Integration Snippet: We provide this code snippet to customers; it is not expected to change frequently.

Backend Architecture

Service Communication Flow:

Nexus: Receives the initial initiate call from the widget. Nexus rate limits requests based on the tenant provided in window.customer, then fetches the Broker deployment configuration for the provided deploymentId.
Origin Validation: If the requesting origin is allowed, Nexus responds with a Twilio Sync session token.
Bot Configuration: The bot config configured in the Broker database deployment is passed to Cortex.
Message Flow: Cortex receives the widget's messages via Twilio Sync and processes them according to the bot configuration.

Replicant Chat Widget - Pen Test Page

About This Deployment

Backend Architecture