Getting Started

This guide provides step-by-step instructions for deploying and configuring the Access Broker in test, staging, pre-prod, and production environments. For detailed information about the concept and functionality of Access Broker, see Overview.

Below is a simplified diagram of Access Broker:

Using this guide, we will install the Britive Access Broker on a Linux-based system and demonstrate its functionality. Here use case is to send a JIT checkout request from Britive Cloud PAM UI and execute a script saved locally on the Access Broker on-premise server/machine.

In the majority of deployments, the Access Broker enables JIT access to remote systems like Active Directory and Linux servers. These systems typically do not run the Access Broker itself but are managed through it.

Deployment Steps

1. This guide assumes that the Britive Cloud PAM tenant is already up and running. Britive Cloud PAM is delivered as a SaaS, so no installation, deployment, or management is required for the tenant itself.

2. Configure and deploy the Access Broker. For more detailed steps, see Configuring and Deploying Access Broker.