Deploying Session Recording with Docker

Britive recommends using Docker to deploy the session recording components. The following steps show an example deployment using this method. This deployment packages the Britive broker and the session daemon under one Docker Compose configuration for a quick setup of ephemeral, recorded user sessions for RDP and SSH.

Prerequisites

Docker Engine and Docker Compose are installed on the target server or virtual machine.
A Britive tenant with the Session Recording feature enabled.
A broker pool token from the Britive admin portal.
Network access from the session daemon to target systems on the applicable protocol ports (e.g., 3389 for RDP, 22 for SSH).

Terminology

Term	Definition
JSON Secret Key	A shared secret used for JSON-based authentication between the Britive broker and the session recording web application. Generated during setup and configured in docker-compose.yml.
Broker	The Britive Access Broker component that is packaged alongside the session daemon. Manages credential rotation and curates ephemeral user sessions.

Setup

Visit https://github.com/britive/onboarding/tree/main/session-recording/docker and copy the directory contents to the desired server or virtual machine.
Update broker-config.yml with the desired tenant subdomain and the token for the broker bootstrap.

Generate a JSON secret key:

On macOS:
```
echo -n "yoursecretphrase" | md5
```
On Linux:
```
echo -n "yoursecretphrase” | md5sum
```

Update the docker-compose.yml file with the generated key:

server:
  environment: 
    JSON_SECRET_KEY: "<json secret key goes here>"

Build the Docker image:
```
docker build -t broker-docker
```
Start the services:
```
docker compose up 
```

This completes the broker and session recording install. The broker service starts automatically, and you should see an instance of the broker running on the Britive admin portal.