Request flow

Trace administrative, campaign admission, and collection requests through P-BitM.

The control plane and campaign plane follow different trust paths. Switch between them to trace authentication, authorization, and workload creation.

Administrative request

1. Open the dashboard

   The operator opens the loopback dashboard over HTTPS.

2. Proxy the API request

   Frontend nginx proxies /api requests to the admin backend.

3. Authenticate the session

   The backend authenticates the opaque server-side session cookie.

4. Authorize the route

   Route-level authorization checks the user role and resource ownership.

5. Read or update state

   The backend reads or updates SQLite and campaign storage.

Campaign admission

1. Open the campaign URL

   An approved recipient reaches the campaign URL through Traefik.

2. Validate routing state

   The campaign service validates routing and tracking state.

3. Exchange the landing state

   The landing flow exchanges valid state for a short-lived signed session token.

4. Admit the WebSocket

   The WebSocket handshake must complete within the configured timeout and admission limits.

5. Create the browser workload

   The campaign service asks the authenticated admin backend to create the target browser container.

Tracking identifiers and stream paths are bearer-like capabilities and must not be written to routine logs or documentation examples.

Collection

Campaign-local clients send bounded, validated records to private collection routes. The campaign service forwards authenticated events to the admin backend, which owns persistence. The dashboard later reads those records through its authenticated API.