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

Azure is a complete cloud platform that can host your existing applications and streamline new application development. Azure can even enhance on-premises applications. Azure integrates the cloud services that you need to develop, test, deploy, and manage your applications

Note: The Session Recording feature is enabled only on request. Please reach out to your customer success point of contact to enable this. Britive Session Recording uses Britive Access Broker to create proxied, short-lived user sessions into servers and

Perform the following steps to configure the Oracle Cloud application in Britive: Note: Before onboarding the Oracle Cloud application in Britive, ensure that you have completed the onboarding prerequisites mentioned in the section Prerequisites . Log in to the Britive application

Perform the following steps to create a user in Oracle Cloud: Login to Oracle cloud console with administrator privileges.  Click Identity & Security from the navigation menu. Select Users from the Identity section . Scroll down the navigation menu and select the

Britive datasets are shipped in two formats: History( ): A daily snapshot of the data taken at the end of the day Latest ( ): The most recent snapshot Britive provides the following out-of-the-box physical datasets: Dataset Name Description access

Britive needs to manage privileges on users and groups in the onboarded Oracle Cloud account. Hence, you need to define policies in the Oracle Cloud account.  Perform the following steps to create a policy in Oracle Cloud: Login to the

notification medium from the dropdown list of notifications and click Add . Click Save .

The following parameters are required as prerequisites for Britive-Oracle Cloud integration: OCID of the tenancy  Name of the tenant  OCID of the user  The private key of the SSL certificate associated with the user  The fingerprint of the SSL

Delegated Admin A tenant admin has all the access rights to all the consumers. A delegated administrator has restricted access specific to a consumer. In this case, the consumer is Secrets Manager. You can apply policies on the resources of

Signals These are the Britive events that can be sent to external receivers. Admins select from this list when configuring receiver mappings. Britive Event Display Name Typical Signal Type user.disable Disable User Account Disabled (RISC) user.enable Enable User

The list below provides a drill-down of previous Britive releases with details about new features, enhancements, and fixes they introduced.  2026 April March February January 2025 November October September August July June May April March February January 2024 November

An identity provider (IdP) is a service that stores and verifies user identities. The default identity provider for any user is Britive. Create and configure an IdP to trust authentication tokens using the following steps: Log in to Britive with

This document explains how to onboard Oracle Cloud applications v2.0 to Britive. OCI v2 is created to support identity domains. For more information, see Managing Identity Domains . Once you have defined the Britive Identity Provider and configured the prerequisites

Installing Broker on CentOS Make sure you have completed all generic prerequisites mentioned in the Prerequisites section. Install OpenJDK 21 using the following command: sudo dnf install java-21-openjdk java-21-openjdk-devel -y Run the following command to

Once you have onboarded the GCP application to Britive, you can scan the organizations and environments. The scans that are submitted are visible in the Scans tab of the onboarded GCP application. Steps for Scanning the GCP application Perform the

Creating an API token API tokens are used for secure API communication. Log in to Britive with administrator privileges. Click System admin -> Security -> API Tokens . Click on the Create Token button. Enter the name and validity of the API token

GA Release 2026.01.01 GA Release 2025.12.02 GA Release 2026.01.01 Released on 28 th January, 2026. Improvements Enhanced pagination and filtering on the My Access page. Added the ability to create and update custom attributes

Britive needs to manage privileges on users and groups in the onboarded Oracle Cloud account. Hence, you need to define policies in the Oracle Cloud account.  Perform the following steps to create a policy in Oracle Cloud: Login to Oracle

GA Release 2024.01.01 GA Release 2023.12.01 GA Release 2024.01.01 Released on January 28 th , 2024. Improvements Added support for GCP Third-party SSO profiles. Fixes An intermittent issue in displaying approval requests on the