Britive Access Broker Configuration

Before you configure a simple “Hello World” use-case, make sure your Britive Access Broker is up and running and showing following screen. I have deployed Access Broker on my MacBook on Apple Silicon M4. Execute the following command on CLI

$ ~/Downloads/britive-broker
$ java -jar britive-broker-0.1.3.jar

java -jar britive-broker-0.1.3.jar
2025-02-19 08:19:42.774 [Thread-0] INFO c.b.broker.service.BrokerStartup -- Starting Britive server access broker….
2025-02-19 08:19:42.775 [Thread-0] INFO c.b.b.service.BrokerBootstrapper -- Retrieving MQTT connection information
2025-02-19 08:19:48.329 [Thread-0] INFO c.b.b.service.BrokerBootstrapper -- MQTT connection information : MqttConnectionInfo(mqttEndpoint=remote.mt1-uw2.dev2.aws.britive-app.com, mqttCredentials=MqttCredentials(username=agent:mt1-uw2-dev2:catapult:7815d90681264d48870ce9b13c3178ef), authTokenKeyName=qZZ1BBYsEWku, requestTopic=agent:mt1-uw2-dev2:catapult:7815d90681264d48870ce9b13c3178ef, respondTopic=$aws/rules/mt1_uw2_dev2_iot_rule_iotAgentMsg/agent:mt1-uw2-dev2:catapult:7815d90681264d48870ce9b13c3178ef, clientId=agent:mt1-uw2-dev2:catapult:7815d90681264d48870ce9b13c3178ef, mqttKeepAliveSeconds=60, mqttDisconnectSeconds=86400, mqttPingTimeoutMillis=5000, mqttSubscribeTimeoutSeconds=10, clientRotateOverlapSeconds=30, maxCredentialSizeKB=20)
2025-02-19 08:19:48.671 [AwsEventLoop 2] INFO c.b.b.service.BrokerLifecycleEvents -- Attempting to connect…
2025-02-19 08:19:50.902 [AwsEventLoop 2] INFO c.b.b.service.BrokerLifecycleEvents -- Connection success! sessionPresent: false
2025-02-19 08:19:50.985 [Thread-0] INFO c.b.b.service.BrokerBootstrapper -- Subscribed to topic: agent:mt1-uw2-dev2:catapult:7815d90681264d48870ce9b13c3178ef

The Britive UI will show the broker as Active

Now configure the “Resource Manger” UI area to provide JIT access to any resource. The resource type could be anything such as EC2, VM, DC Server, Router, Firewall, SSH system, Active Directory, K8S, etc. Britive is really powerful and extend JIT and ZSP functionality to any on-prem, off-premises, colocation, Edge, or branch location with its common policy model.

In my example I will simply print “Hello to Britive World” on the screen as a test. Later I will show how to control and manage access to a routing or firewalling device in next post.

Resource Type