The Secretless Broker relies on its configuration to determine which Target Services it can connect to and how it should retrieve the access credentials to authenticate with those services.

Each Secretless Broker configuration includes two sections:



listeners A list of protocol Listeners, each one on a Unix socket or TCP port.

A list of Handlers to process the requests received by each Listener. Handlers implement the protocol for the Target Services and are configured to obtain the backend connection credentials from one or more Secret Providers.

In the examples below, we share the Secretless configurations that were used in the Quick Start. For ease of understanding, we've broken them up into three separate configurations. In practice you can configure Secretless Broker to handle as many types of connections as you need; to see how we configured Secretless Broker to handle all three of these connection types at once, check out the actual configuration we used in building the quick start Docker image.

Configuring Secretless Broker

The Configuration Managers section in the Secretless Broker reference has more information about how to provide the Broker with its configuration in practice.