Integrating to internal infrastructure with Broker

Published on December 20th, 2022


The Broker connection is designed to connect Roadie and its plugins to integration targets that are located on self-hosted infrastructure and therefore not publicly available via the internet.


The broker is a Node.js service that you run inside your infrastructure to provide a secure tunnel for Roadie traffic. It was originally created by security company, Snyk. The code is open-source. We are actively using it with existing customers for Kubernetes API access and other Backstage and Roadie plugins. You don’t need to be a Snyk user to use the broker.

The benefits of the broker include:

  • You can allow list what Roadie can access using a config file.
  • Any tokens for the internal endpoints stay in your infra. They are not shared with Roadie.
  • The broker maintains an audit log of what we access.
  • The connection is established outbound from your side. We cannot re-establish the connection on our own if you kill it.

The Broker feature is available on our Growth Plan - see pricing page for more information.

Broker Architecture

Broker connection consists of two similar services called broker server and a corresponding broker client

Client A node.js application creating a websocket connection to its counterpart, broker server hosted in Roadie infrastructure.

Server A tenant specific broker server accepting websocket handshakes and directing traffic through from Roadie instance via the socket to the broker client

The broker connection itself keeps an open websocket identified by a broker token which can be specified by the client trying to establish a connection. The traffic flows through this websocket and is filtered on both ends, broker server and broker client, using an ‘accept.json’ configuration file. This configuration file also determines where requests are forwarded to and if they need additional headers to be injected to the request.

This way Roadie does not need to have knowledge or access of your infrastructure endpoints nor authorization tokens.


Enabling broker connection

The broker server instance is not enabled by default on tenants and thus needs to be requested to be enabled.

Once enabled the broker server is exposed in a URL The broker endpoint is secured by allow listing IP addresses. To set up broker connections you need to provide IP ranges where your broker clients are hosted so those can be configured to come through.

Configuring Broker client

Broker client application

Broker client is a Node.js application which can be deployed as a Docker container into internal infrastructure. Roadie can provide Dockerfiles to construct broker client application by request, depending on the plugin. Alternatively Roadie can provide a base broker image Dockerfile which can be reused and enhanced with multiple different configuration files.

Running the broker client application

The broker client can be installed and run as a standard node.js service. You can install the broker client when you have node.js and npm installed with a command npm install --global snyk-broker. After the global broker application is installed, you can run it with a command broker --verbose with verbose logging.

Alternatively you can deploy the broker application as a container. Below you can find a base Dockerfile that can be used to construct the broker client image.

Base Dockerfile
FROM snyk/ubuntu as base


USER root

RUN apt update && apt install -y make python gcc

RUN apt-get update && apt-get install -y ca-certificates

ENV NPM_CONFIG_PREFIX=/home/node/.npm-global

ENV PATH=$PATH:/home/node/.npm-global/bin

RUN npm install --global snyk-broker

FROM snyk/ubuntu

ENV PATH=$PATH:/home/node/.npm-global/bin

COPY --from=base /home/node/.npm-global /home/node/.npm-global

COPY --from=base /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt

# Don't run as root
WORKDIR /home/node
USER node


CMD ["broker", "--verbose"]

Example Run command

docker run --env-file broker-env -v ~/accept.json /home/node/accept.json my-built-broker-client-image

Standard broker environment variables

Broker client expects a standard set of environment variables to run with good configuration. In the example above we mounted and environment file called broker-env. The values within that file, without additional values that might be defined in individual configuration files, can be found below:


Note the volume mount of an accept.json file from the home folder to the container. This accept.json file will be different based on the plugin (or plugins) that the broker client is built to support. Alternatively you can also build different images and that contain the required accept.json and use the COPY Dockerfile instruction to populate the image with the wanted config. See more information about configuration files below.

Broker client application configuration

Broker client is configured via an accept.json configuration file and environment variables based on the content of the said accept.json file. The file contains endpoint routing paths definitions determining where the requests coming from Roadie should be forwarded to. The configuration file also acts as a filtering mechanism to block non-allowed requests and as a request decorator to enhance request headers with possible auth information.

Roadie can provide configuration files for plugins which can be used to forward traffic to endpoints the plugins are using. You can find a broker configuration file section on each of the plugins documentation pages. If some plugin is missing a configuration file, you can request the support to provide you with one.

Configuration file structure

An example accept.json looks like the following:

  "private": [
      "//": "Show results of my plugins API",
      "method": "GET",
      "path": "/api/show",
      "origin": "${MY_PLUGIN_REST_ENDPOINT}",
      "auth": {
        "scheme": "bearer",
        "token": "${MY_PLUGIN_AUTH_TOKEN}:"
  "public": [
      "//": "Get broker connection status",
      "method": "GET",
      "path": "/healthcheck"

The file is divided into 2 parts, public and private.

The public configuration block defines what endpoints can be called when calling the broker client endpoint directly. This would be for cases where an internal infrastructure would need to send data via the broker client toward Roadie instances. This is rarely used since most Backstage and Roadie plugins make requests and expect a response.

The private configuration block defines what requests are allowed to come through via the connected broker websocket connection and where they are forwarded to. In the example above we are allowing traffic to flow to a single endpoint matching an imaginary service we have developed. We are hosting this custom imaginary service in our own infrastructure behind a corporate firewall in a private network and it’s APIs are accessible when using bearer token authentication. The service exposes a single GET endpoint with a path /api/show. With this configuration the broker client would allow Roadie plugins to contact the imaginary service, via the broker connection, in cases where the request is going to the defined endpoint using a GET request and nothing else.

The best way to configure endpoints and tokens via environment variables. In the above example the accept.json file is expecting two env variables, MY_PLUGIN_REST_ENDPOINT and MY_PLUGIN_AUTH_TOKEN.

Configuration options

Below you can find a table of configuration options available in the accept.json file.

Key Example values Description
// Any string Denotes a comment on the configuration file
method HTTP Methods (GET, POST, PUT, DELETE, etc.) or any HTTP Method to be used as a filter on the request
path /my-plugin/endpoint Endpoint path to accept requests to. Only request going to these endpoints are forwarded. You can use * as a wildcard, e.g. /my-service/components*
origin The origin host to forward the request to. This is only available on the private configuration block.
auth {“scheme”: “bearer”, “token”: “my-secret-token” } Auth scheme and value to use to overwrite any auth header coming from the original request. See auth scheme options from the table below. This is only available on the private configuration block.

Auth Scheme options

Scheme value Value input key Example End result
token token { "scheme": "token", "token": "my-secret-token" } Authorization: Token my-secret-token
bearer token { "scheme": "bearer", "token": "my-secret-token" } Authorization: Bearer my-secret-token
basic token or username and password { "scheme": "basic", "token": "my-secret-token" } or { "scheme": "basic", "username": "user", "password": "pass" } Authorization: Basic bXktc2VjcmV0LXRva2Vu (base64 encoded token) or Authorization: Basic dXNlcjpwYXNz (base64 encoded user:pass)

An additional filtering based on any header can be achieved by using valid configuration block in the configuration file.

"valid": [{
  "header": "my-header-key",
  "values": ["my-super-secret-header-key-value"]