Prerequisites
A broker can run on any OS that can run a Java Virtual Machine (JVM)/Java Development Kit (JDK).
Britive supports Windows services and Linux OS, which supports the systemd services for running the broker as a service.
Broker service installers are provided for Microsoft Windows MSI and Linux OS Debian packages.
A broker can run on any modern CPU with a RAM requirement of 100 MB.
The broker requires an outbound HTTPS (TCP port 443) connection to the Britive SaaS platform. Configure your firewall or security group to allow outbound/egress traffic to https://${britive.tenant.subdomain}.britive-app.com. This enables the broker to establish and maintain connectivity with your Britive tenant.
If permission scripts are not stored locally, ensure outbound/egress access is allowed to the external location where they are stored.
For example, if the scripts are stored on an AWS S3 bucket named resource-permission-data.s3.us-west-2.amazonaws.com, then the security group configuration must explicitly allow access to this endpoint.
Ensure that the Java Development Kit (JDK) is installed on the OS.
Downloading and installing the broker
Log in to Britive.
Click on Admin -> Brokers and Broker Pools.
Click on the Download Brokers button.
Expand the package type to view available installers, and click on the required installer to download the package. Users can also copy the link, allowing them to download the broker from a location other than the local machine or browser.
Install the broker on the required OS:
Generic (.tar, .zip, .jar packages)